There's a DNS problem in some areas for DU

[bananas]

www.democraticunderground.com isn't resolving in some areas,
I had to put it in the hosts file to post this.
Here's the output from cache check at opendns:

http://www.opendns.com/support/cache/

Results for www.democraticunderground.com

United States

Chicago, Illinois, USA
* 216.158.28.195
* 216.158.28.197
* 216.158.28.199
* 216.158.54.195
* 216.158.54.197

Dallas, Texas, USA
* 216.158.28.195
* 216.158.28.197
* 216.158.28.199
* 216.158.54.195
* 216.158.54.197

Los Angeles, California, USA
* NO RESPONSE

Miami, Florida, USA
* NO RESPONSE

New York, New York, USA
* 216.158.28.195
* 216.158.28.197
* 216.158.28.199
* 216.158.54.195
* 216.158.54.197

Palo Alto, California, USA
* 216.158.28.195
* 216.158.28.197
* 216.158.28.199
* 216.158.54.195
* 216.158.54.197

Seattle, Washington, USA
* 216.158.28.195
* 216.158.28.197
* 216.158.28.199
* 216.158.54.195
* 216.158.54.197

Washington, DC, USA
* 216.158.28.195
* 216.158.28.197
* 216.158.28.199
* 216.158.54.195
* 216.158.54.197

International

Amsterdam, The Netherlands
* NO RESPONSE

London, England, UK
* NO RESPONSE

Singapore
* NO RESPONSE

[steve2470]

1. I might post something in Ask the Administrators for Skinner and Elad nt

[kenny blankenship]

2. I can confirm . for ATT Southeast nameservers www.democraticunderground.com does not resolve

also my own nameserver ignores the ISP nameservers and goes to root servers. That was the first sign of dns failure.

I put in opendns servers in my resolv.conf file to get here.

[bananas]

7. The google servers work, but not verizon

google and verizon run public anycast dns servers:


>nslookup www.democraticunderground.com 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: www.democraticunderground.com
Addresses: 216.158.28.197, 216.158.28.199, 216.158.54.195, 216.158.54.197
216.158.28.195


>nslookup www.democraticunderground.com 4.2.2.1
Server: vnsc-pri.sys.gtei.net
Address: 4.2.2.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to vnsc-pri.sys.gtei.net timed-out

[kenny blankenship]

8. Try root nameservers

Root Nameservers No home.

Example: nslookup - 202.12.27.33
> democraticunderground.com
Server: 202.12.27.33
Address: 202.12.27.33#53

Non-authoritative answer:
*** Can't find democraticunderground.com: No answer

ISP nameservers won't know what root servers won't know.

Well, I should backtrack and say that *DU* isn't known to root nameservers. It's not that the root servers are incommunicado. Du has a problem with its service provider updating its DNS entries, it would appear.


; Use "dig @A.ROOT-SERVERS.NET . ns" to update this file if it's outdated.
; This file holds the information on root name servers needed to
; initialize cache of Internet domain name servers
; (e.g. reference this file in the "cache . <file>"
; configuration file of BIND domain name servers).
;
; This file is made available by InterNIC
; under anonymous FTP as
; file /domain/named.cache
; on server FTP.INTERNIC.NET
; -OR- RS.INTERNIC.NET
;
; last update: Dec 12, 2008
; related version of root zone: 2008121200
;
; formerly NS.INTERNIC.NET
;
. 3600000 IN NS A.ROOT-SERVERS.NET.
A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4
A.ROOT-SERVERS.NET. 3600000 AAAA 2001:503:BA3E::2:30
;
; FORMERLY NS1.ISI.EDU
;
. 3600000 NS B.ROOT-SERVERS.NET.
B.ROOT-SERVERS.NET. 3600000 A 192.228.79.201
;
; FORMERLY C.PSI.NET
;
. 3600000 NS C.ROOT-SERVERS.NET.
C.ROOT-SERVERS.NET. 3600000 A 192.33.4.12
;
; FORMERLY TERP.UMD.EDU
;
. 3600000 NS D.ROOT-SERVERS.NET.
D.ROOT-SERVERS.NET. 3600000 A 128.8.10.90
;
; FORMERLY NS.NASA.GOV
;
. 3600000 NS E.ROOT-SERVERS.NET.
E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10
;
; FORMERLY NS.ISC.ORG
;
. 3600000 NS F.ROOT-SERVERS.NET.
F.ROOT-SERVERS.NET. 3600000 A 192.5.5.241
F.ROOT-SERVERS.NET. 3600000 AAAA 2001:500:2F::F
;
; FORMERLY NS.NIC.DDN.MIL
;
. 3600000 NS G.ROOT-SERVERS.NET.
G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4
;
; FORMERLY AOS.ARL.ARMY.MIL
;
. 3600000 NS H.ROOT-SERVERS.NET.
H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53
H.ROOT-SERVERS.NET. 3600000 AAAA 2001:500:1::803F:235
;
; FORMERLY NIC.NORDU.NET
;
. 3600000 NS I.ROOT-SERVERS.NET.
I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17
;
; OPERATED BY VERISIGN, INC.
;
. 3600000 NS J.ROOT-SERVERS.NET.
J.ROOT-SERVERS.NET. 3600000 A 192.58.128.30
J.ROOT-SERVERS.NET. 3600000 AAAA 2001:503:C27::2:30
;
; OPERATED BY RIPE NCC
;
. 3600000 NS K.ROOT-SERVERS.NET.
K.ROOT-SERVERS.NET. 3600000 A 193.0.14.129
K.ROOT-SERVERS.NET. 3600000 AAAA 2001:7FD::1
;
; OPERATED BY ICANN
;
. 3600000 NS L.ROOT-SERVERS.NET.
L.ROOT-SERVERS.NET. 3600000 A 199.7.83.42
L.ROOT-SERVERS.NET. 3600000 AAAA 2001:500:3::42
;
; OPERATED BY WIDE
;
. 3600000 NS M.ROOT-SERVERS.NET.
M.ROOT-SERVERS.NET. 3600000 A 202.12.27.33
M.ROOT-SERVERS.NET. 3600000 AAAA 2001:DC3::35
; End of File

-=-=-=-=-

I took the advice from the top of named.ca and re-upped my root servers list, replacing the original copy. Restarted named, still no resolving. (No resolving DU, that is.)

[DainBramaged]

23. Verizon hates the DU

here's proof

[CaliforniaPeggy]

3. What is DNS?

[L. Coyote]

5. Domain Name Service

you ask for "http://gop.nuts" and the DNS server says, "Call the computer with the RNC server IP address.

[CaliforniaPeggy]

6. Thanks!

[Sonoman]

26. Whew! I was too embarrassed to ask.

Sometimes, I think I am one of the last people on the planet who doesn't know what all these letters mean.

I had to finally ask what 'ISP' means, the other day.

Internet Service Provider.

duh....

Sonoman

[CaliforniaPeggy]

28. My dear Sonoman!

There's so much I don't know that I can't afford to be embarrassed!

I knew ISP, but not the others.

And I still don't understand at all what happened...

:hi:

[Sonoman]

29. Maybe you and I should start a Support Group.

Yeah, that's it!

Just us, the two of us.

Did you get any of that snow down South?

Sonoman

[CaliforniaPeggy]

32. LOL!

There was quite a lot of snow (for us) on the local mountains. I wasn't able to get any pics though...

Just too much going on.

:hi:

[L. Coyote]

4. There was a DNS problem on the WWW this morning in the USA.

Cross-country requests were timing out

[CaliforniaPeggy]

9. I just posted a link to this thread in ATA.

I know they scan the threads there so they might spot this right away. I hope so.

[steve2470]

10. ty CalPeggy, you rock ! nt

[CaliforniaPeggy]

12. Aw, thanks, sweetie...

[MineralMan]

11. It's working OK here in Minnesota, via Comcast.

And Comcast blows big-time with its DNS server. I'll check, but I don't think I'm using the free Google server right now.

[slackmaster]

13. A query in my area returned NS1 and NS2.BADWHOISSHUTDOWN.COM

...as the authoritative nameservers for the domain.

HTH

[slackmaster]

14. And the problem is still spreading

I just put an entry in my hosts file to make it keep working:

216.158.54.197 www.democraticunderground.com

[necso]

15. I was getting it more widely

yesterday (when you can't link google -- you know you have a problem).

And yeah, I know about alternative DNS servers (I have something of a technical background), have a list.

It'd be good to have short list of IP#'s for important sites that people could put in their hosts file.

More generally, folks, it's super helpful to know a few basics, or at least to know someone who does and that you can call.

...

Oh, and you (not the op, of course) know better; so I'll consider it humor.

Add five random words here.

[necso]

33. Maybe I should be more forthcoming sometimes;

but it doesn't come naturally, easily to me.

It's a matter of agreeing to terms (...) and sticking to them.

...Fairly quickly, I imagine.

[steve2470]

16. off-topic: anyone else noticing avatars not showing up here ? nt

[TommyO]

17. Just an FYI - admins are aware of this and working with DU's ISP to ID and resolve the issue.

[FSogol]

18. Cool, keep up the good work.

They must have fixed something, because I couldn't get on for about 2 hours.

[tahrir]

19. likewise

gl

[steve2470]

21. yes great work, as always nt

[DainBramaged]

20. 666

always works


WORKIE GOOD NOW, MAYBE DU HAS A PU DNS

[prairierose]

22. Thank you for posting this..I thought I was going crazy...

I am in the midwest so it is probably the Chicago problem affecting me....That was scarey...not being able to get DU....:scared: I rely on this place for the latest news of importance as opposed to the "news" I do not care about that the corporate media spews.

[JuniperLea]

24. Wow... was out for me most of the morning!

Scary... I thought DU pissed Anonymous off or something! :D

[brendan120678]

25. It was out for me for a few hours...

this afternoon (near Hartford, CT)

[Tsiyu]

27. Have had an hour's trouble after storms here

FInally got on the DU, but I couldn't get Google, either, for a minute.

Some of you computer savvy folks : feel free to tell the rest of us how to get on when this happens.

Thanks... and glad to have my DU

[adamuu]

30. Confirmed in Albany NY (roadrunner) n/t

[muriel_volestrangler]

31. Still not working for me in England

I'm having to run with a workaround in the hosts file too .

[MilesColtrane]

34. I haven't been able to pull up the site here in Dallas since 1:30pm CT.

democraticunderground.net and democraticunderground.org similarly do not respond.

Using a Canadian proxy server now.

[Generic Other]

35. Still using proxy through canada

in Pacific NW.

[kentuck]

36. Confirmed in Colorado Springs.

I was off line for 5 or 6 hours but have had no problem since I signed on??