• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

www.buchanan.org censored? DNS seems to fail for that site.

VirtualLarry

No Lifer
My buddy called me up, can't get to Pat Buchanan's web site. Googling for the address, it comes up as www.buchanan.org . Attempting to browse for that immediately fails, and attempts to ping it result in "host not found" errors, indicating that the DNS lookup failed.

I'm on Verizon, and my buddy is on Comcast. Widespread censorship?

Edit: someone on sat. internet in nh was able to access it. Looks like widespread dns blacklisting by major isps to me.
 
Last edited:
VirtualLarry - What IP are your nslookups resolving to? I resolve to 74.52.139.242 and the page loads fine.

It's possible that they have changed hosts and your DNS server is not updated yet...
 
VirtualLarry - What IP are your nslookups resolving to? I resolve to 74.52.139.242 and the page loads fine.

It's possible that they have changed hosts and your DNS server is not updated yet...

I generally just use ping to convert a DNS name into an IP, and it gives a "host not found" error, which generally means that the DNS is not resolving.

What ISP are you on?

Edit: Putting that IP into my web browser, and I get an intro page, "Great Success !
Apache is working on your cPanel® and WHM™ Server"

C:\Users\Larry>nslookup www.buchanan.org
Server: DD-WRT
Address: 192.168.2.1

*** DD-WRT can't find www.buchanan.org: Server failed

C:\Users\Larry>nslookup www.google.com
Server: DD-WRT
Address: 192.168.2.1

Non-authoritative answer:
Name: www.l.google.com
Address: 66.249.81.104
Aliases: www.google.com
 
Last edited:
No name resolution for FQDN www.buchanan.org.

Take off the tinfoil hat though, probably just a DNS problem with the sites name server.

If it were just a DNS problem with the site's DNS servers, then shouldn't both OpenDNS and smaller regional ISPs also have a problem accessing the site? I mean, shouldn't it be down for everyone, rather than just being down for the two biggest national ISPs?
 
If it were just a DNS problem with the site's DNS servers, then shouldn't both OpenDNS and smaller regional ISPs also have a problem accessing the site? I mean, shouldn't it be down for everyone, rather than just being down for the two biggest national ISPs?

No. It would depend on if that name server had a record cached for the FQDN, otherwise the resolving name server would have to contact the name server for the domain.

If there is a problem with the authoritative name server you'd only see a problem if the resolver had to contact it, like if it didn't have a cached entry.
 
It must be this time of the year when Mars and Venus are perpendicular to Earth. :hmm:



😎
 
Back
Top