US Cable Support > Comcast HSI > [DNS] 04-2005 Connection Problems - Discussion

reply to File Quit

Re: [DNS] We have another issue tonight...

reply to File Quit
I'm a little bit new but how do you switch the DNS because this is the only website I can go to right now.

reply to HotRodFoto
Switch your DNS my friend! 4.2.2.2 in your Network settings of your computer or in your router. See instructions here:

»Comcast High Speed Internet FAQ »How do I change what DNS server my computer uses?
--
Apple rules!!! Get an iPod and iBook today, what's to lose? »www.apple.com

reply to File Quit
I'm in South jersey where all is fubar again. Switched over to 4.1.1.1 and cruising along.

reply to File Quit
I've always kept the 4.2.2.x's in there so I'm not seeing a problem and am also glad to have some connectivity for the moment (they are actually GTE's DNS's IIRC).

But I do recall in this thread: »[DNS] DNS Outage is Resolved - Please Read that we were told there would be "no repeat". Oh well.

reply to Romeo21779
see my above post Romeo.

reply to Blam
They are different for people accross the country. it uses IP geography to figure out the DNS server closest to you and sends you to that. Mine for instance is a GTEI server in Chicago, others are level3 and verizon.
--
Apple rules!!! Get an iPod and iBook today, what's to lose? »www.apple.com

reply to waver168
This is the so pissing me off.... Down in Pittsburgh, Pa as well 2 times in one week here we go again...changed the dnas on my router....now im good to go...freaking comcast gotta love em...biggest isp in the world! maybe not the greatest..

reply to File Quit
Plano,Texas, Huge DNS problem here too, switching to 4.2.2.2 did the trick.

reply to ravenous67
No DNS here in New Hampshire (Boston area) either. Had to add 4.2.2.2 to my router. Lucky that's an easy IP to remember.

This is twice in as many weeks now. They should have kept the ATTBI nameservers when they switched over.
--
SMTP: Spam and Malware Transfer Protocol. Also used on rare occasion to transmit e-mail messages.

reply to aiiee
sorry, it was 4.2.2.1 not 42.1.1

here's a couple more USA ones that work:

199.166.28.10 Atlanta
199.168.31.3 Orlando
199.5.157.128 Detroit

reply to File Quit
Just started here in Albuquerque too. Checked my router logs and saw a host of port 53 entries. Relaced Comcast DNS with three of the ORSC ones and I am off and running.

I wonder if "We fixed the DNS problem..." belongs in the list of the greatest lies. Right up there with "The check is in the mail"
--
"If you pick up a starving dog and make him prosperous, he will not bite you. This is the principal difference between a dog and a man."----- Mark Twain

reply to File Quit
Yep bad in Arkansas as well. Switched DNS servers and running fine now. Funny thing though, I had the Comcast DNS servers set as First and Second(not using DHCP for DNS resolution-added them manually) and added a third 199.166.24.253(ORSC Public Access DNS) as a backup but that didn't seem to help. What is the point of adding that one if it doesn't work unless I did something wrong?

Not gonna happen again! Yeah right!!

reply to File Quit
Tucson has the same DNS issues, switched to 4.2.2.6. Same crap as last week.

reply to File Quit
Down in SoCal...switching over to 4.2.2.2 again...

reply to File Quit
Problem solved. I though this was supposed to be a one time thing, but I have been getting outages here all week.(Michigan)

reply to LoPhatPhuud
I wonder if "We fixed the DNS problem..." belongs in the list of the greatest lies. Right up there with "The check is in the mail"
-----------------------------------
Yes, big mess here.
--
Best Team.

reply to chuck1234
It is down here in Citrus Heights as well.....

reply to File Quit
Down again in 18954. This is getting ridiculous.

reply to File Quit
Problems here as well. So much for the "preventative measures" they put in place to try and avoid this same thing from happening.

Switching to 4.2.2.2 and 4.2.2.3 fixes everything. Come on, Comcast. Get your stuff together.