DNS problems (in General)

bartjan May 20 2006 12:31 PM EDT

This is the second time today that the ISP gandi.net is unreachable from just about every place I can check from.
This happens to be the ISP that runs the nameservers for both carnageblender.com and utahpython.org (the server that runs the themes and some static files).
Because of this, once the cache of the nameserver of your own ISP has expired, you will have a very hard time playing CB (or need to be skilled enough to work around it).

Jon, if you need secondary nameservers that are unrelated to gandi.org, I could provide you with one (or a few).

AdminQBnovice [Cult of the Valaraukar] May 20 2006 12:41 PM EDT

Whew I thought I was getting messed with.

I've been playing using the ip all morning, the problem is going to be
the root nameservers failing to update for a full 24 hours, better to get the existing nameservers back up and online.

bartjan May 20 2006 12:44 PM EDT

If impatient, the following 2 lines, when added to /etc/hosts will fix it for you. I think Windows has a similar file, burried deep in C:\windows. Note: only use this temporary, as this won't track any future changes: cb2.carnageblender.com carnageblender.com www.carnageblender.com utahpython.org

th00p May 20 2006 12:44 PM EDT

It's surprising how few people stayed on CB while it was down, the number was down to around 10 I believe.

In case of another gandi.net failure, you can still use that to access the CB site to continue playing. You may want to bookmark that for a later date, as I did.

bartjan May 20 2006 12:48 PM EDT

That's not enough in situations like this, as the theme server also depends on the same ISP for their DNS. Yes, you could access CB by IP, but each page took ages to load...

AdminQBnovice [Cult of the Valaraukar] May 20 2006 12:49 PM EDT

thankfully I think my theme is still being cached by my browser...I'd die without my modern mono...

AdminNightStrike May 20 2006 3:08 PM EDT


bartjan May 20 2006 3:21 PM EDT

lmhosts.sam is for the local network (when it's not named .sam(ple)). The directory sounds like the right one, there should be a hosts file as well there.

bartjan May 21 2006 11:39 AM EDT

A DDOS attack is what caused it.
This thread is closed to new posts. However, you are welcome to reference it from a new thread; link this with the html <a href="/bboard/q-and-a-fetch-msg.tcl?msg_id=001oKJ">DNS problems</a>