Fsck.

[coyoteden.livejournal.com]

Comcast DNS just died. Again.
Just as thousands of their subscribers are going to need to download Windows Updates.

4.2.2.1/4.2.2.2 is your friend.

Comments

[110billion.livejournal.com]

Hence i rely on MCI's DNS. *pats them*

[teraflops.livejournal.com]

I am so glad I don't work tier support tonight.

[coyoteden.livejournal.com]

At the moment you can't even get through on the phone. It's just busy.

[rwmidl.livejournal.com]

According to Comcast.net the network is healthy :)

Oh, the network is fine, it's the damn DNS that up and died.

[coyoteden.livejournal.com]

I guess they haven't had time to update their status. Just for laughs I tried to call about an hour after it started. It would either ring busy or "can't connect your call" after you went thru the menus. Totally phonedotted.

I know I'm precahing to the clueful, but when something like this happens, if you put those IPs as DNS servers in your router or IP config you will be back online.

Re: Oh, the network is fine, it's the damn DNS that up and died.

[rwmidl.livejournal.com]

I run my own DC in my house. Months ago I set up Level 3's DNS servers in the DNS forwarders (as well as Comcast and my work DNS server) so I have a pretty good balance :)

Re: Oh, the network is fine, it's the damn DNS that up and died.

[rwmidl.livejournal.com]

Also, I found this on BBR..it's a list of "good" DNS servers..

http://www.dslreports.com/forum/remark,13154925~root=comcast~mode=flat

Re: Oh, the network is fine, it's the damn DNS that up and died.

[tjernobyl.livejournal.com]

The frontlines have absolutely no connection to the actual network administration. If a problem was found, it'd only be because someone with power has comcast at home for whatever reason.

[lissrac.livejournal.com]

I am barely on here right now, I am currently on comcast. Every other second I seem to lose network connectivity

[jecook]

Bleck.

I have a list of other provider's DNS I use, just in case.

Except qwest, as they have this ultra nasty ass habit of changing their server without telling anyone.

[(Anonymous)]

trust me, tech support and billing are not happy places to be where comcast is concerned tonight. ick. the boards at work are saying that all new areas are being effected - though I'll guess and say it's all of the usa that uses comcast. anyone with an account number not starting with an 8 want to confirm that one? *L* where we work, it was 10 min's wait for a rep when I left. not all that bad... I've seen worse.

[bamatone.livejournal.com]

Yes. I am one of the masses... Jeers to Comcast.

I don't know if you noticed, but C|NET had an article (http://news.com.com/DNS+issue+hobbles+Comcast/2100-1038_3-5660518.html) about the last outtage. Now it says it lasted about 6 hours, but the original article had Comcast stating it was fixed in about one hour. Fucking liars. Too many people must have called bullshit, and so the article was ammended later.

[inahandbasket]

And here i was wondering if it was just me.
What're the two ips?

[tupper.livejournal.com]

Root DNS servers.

[oggsmith.livejournal.com]

i was at a friends place tonight and he has comcast. we couldn't get online and when we called comcast after choosing their options the message said something to the effect of we are experiencing global issues with our network. i about died laughing.

Not quite geeky enough...

[bean-frog.livejournal.com]

What's 4.2.2.1/4.2.2.2?

Re: Not quite geeky enough...

[coyoteden.livejournal.com]

4.2.2.1/4.2.2.2 (all the way up to 4.2.2.9 i think) are alternate DNS servers you can use if the ones provided by your ISP fail. Just put them in your router or OS and you are good to go.

These nameservers are easy to remember and run by Verizon directly on the backbone, so the likelihood of them failing is low.

Re: Not quite geeky enough...

[bean-frog.livejournal.com]

Ahhh, it all makes sense now, thanks! :o)

[sunfell.livejournal.com]

Ah, so it wasn't my occasionally balky and stubborn router. I couldn't get email or anything, although for a while I was somehow 'stuck' on LJ and able to do stuff within its confines.

So, I just did my virus scans and other maintenance on my system and called it a night. Got my Comcast email this morning, so I am assuming that it's back up.

[gholam.livejournal.com]

NetVision (http://www.netvision.net.il), the oldest ISP in Israel, used to have their DNS servers open to all - 194.90.1.5, 199.203.1.20. This led to everyone and their dog using them, regardless of what ISP they subscribed to, because every network guy remembered these two by heart, and punched them in whenever they needed a DNS server, because these servers were absolutely rock solid and 100% available.

This went on for 10 years or so.

Enter February 2005. NetVision admins finally get tired of constant hammering on their DNS servers, and close them to everyone except actual NetVision subscribers.

Guess when happened the next day... and the next day... and the day after that...

[lordstorm.livejournal.com]

Er, I'm guessing Comcast is an ISP then? *blank look*

[teriwyn.livejournal.com]

I'll take a guess that you don't live in the United States, then?

(That wasn't meant to be snarky ... I've read it a couple of times, and it *could* sound that way -- I don't mean for it to.)

Comcast is the huge US cable company / cable ISP that made a bid to buy Disney in the not too distant past. That was after they gobbled up AT&T's Cable TV and cable broadband divisions. Yummy!

[infy.livejournal.com]

Okay, yes, this would explain a lot. I was just too lazy to look up what the problem was and played games instead.

[teriwyn.livejournal.com]

Fortunately, I left Comcast back in 2003. I stopped working their front lines in 2002, anyhow...

During 2003, they had DNS issues repeatedly over the course of a couple of months in my region, and then the issues just stopped. (Obviously I don't believe that. I know they made infrastructure changes that they didn't tell people about.)

Now, on a national level, it looks like they've outgrown their DNS infrastructure again. The inside scoop (and I'm not sure how "inside" it really is, since I haven't read any news about it -- this could be all over the place) is that they're talking about tripling capacity very soon. Because this is about the third or fourth time in not as many weeks that this has happened for a number of hours.

Fortunately for my boyfriend, his shift ends at 7pm. Not like he'd have to do anything except tell the agents to say, "Yes, we know... no ETA." over and over again, anyhow. (Internal Helpdesk, not a supe.)