AHHH! DNS issues....

[Fallen Kell]

Hi everyone.

This is more of a vent then a question for help (sorry it is just REALLY frustrating!).

Well, my Comcast DNS server is down (AGAIN!!!). I think this is really the only problem I have ever had with Comcast. The only thing is this is at least the 40th TIME! Now I don't fully blame Comcast, I do have a router is not able to get the DNS server from Comcast's DHCP request (although I don't know why it doesn't pull this anymore, it did origionally). Anyway, because of this (and the fact that I think ahead for issues like this), I keep a list of known public DNS servers.

So since my Comcast DNS server is down, I switched to one of the known public servers and at least get me back on the internet working again. I decide to try and use the "Online Chat Helpdesk" at Comcast to simply ask for the current DNS server I should be using. Now I really should have known better, but still I was hoping to get someone who might know a little about how things work and not a direct read the chart for the problem, type the solution person. But that is asking too much. I REALLY don't want to call up comcast's tech support, but that looks like what I will have to do.

The person on the chat was very nice, but couldn't get me a DNS server IP address (didn't even know what one was...). The conversation was basically I am paraphrasing:

what is your problem?

The DNS server I use is not responding. Can you tell me the IP address of the correct DNS server that my system should be using?

I am showing your connection is fine.

Yes. The connection is not the problem. The issue is the DNS server is down.

If you are having problem with a server, how are you even connected?

The DNS server is what changes www.comcast.net to 204.127.205.8
It is basically a lookup that matches names to IP addresses.

I am sorry sir, but I can not help with this problem.
You or the account owner needs to call up the help number.
Is there anything else I can help you with?


AHHHH!!!! Again, sorry everyone. I really REALLY needed to vent.

 

[ivwshane]

So what's wrong with just sticking with one of the public dns servers?

 

[Nocturnal]

They probably don't even know what the OSI model is so for them to even begin to understand DNS, it's too hard for them.

 

[Fallen Kell]

Well, I guess the main problem with the public ones is that they have not been too stable lately (these are from the http://www.opennic.unrated.net/ project, which has slowly been dying over the last 2-3 years). Anyone know of other good public DNS servers?

 

[kevnich2]

Try these: 4.2.2.1 - 4.2.2.6 These are Level3's DNS servers. These work perfectly for me whenever I have DNS issues (RR had issues a while back, have been fixed recently though)

 

[fredfillis]

Originally posted by: Fallen Kell
but couldn't get me a DNS server IP address (didn't even know what one was...).

Having the same problem here (MD) as of around mid day yesterday (11/30). Called Comcast last night and of course they had no clue. I suspected their DNS was down and told the "tech" that and he confirmed there was a DNS problem "in my area". Then he was going to send out a tech to re-synch my modem. Hardy har har, so this tech is going around to all the comcast customers who are out in order to re-synch all their modems as well?

When I asked the "tech" to confirm the DNS IP addresses he basically said that they can't do that as it could lead to someone hacking into my connection.

Ok, I give up with these people. Does anyone out there have a phone number that gets you into a real tech at Comcast?

Meanwhile, back at the ranch, I will be configuring my router to use non-comcast DNS servers in the future. Check this out http://www.dslreports.com/forum/remark,13154925