Printable View
I have tried connecting both from my home PC and from my work PC and even though they use completely different DNS servers www.sans.org is not resolving.
I am getting the error:
Unable to determine IP address from host name for www.sans.org
Is anyone aware of SANS being hacked or DoS'd? Is this some sort of cache poisoning?
Or- are they just down right now for some reason??
I get a host unknown from a ping here, their (or their providers) DNS must be down.
Hmm...got some spam from them this morning...kinda wish I hadn't permantly deleted it now...
Here is what I get (using a regional university as dns server)
> server ns1.msstate.edu
Default Server: ns1.msstate.edu
Address: 130.18.80.12
> set debug
> set d2
> www.sans.org
Server: ns1.msstate.edu
Address: 130.18.80.12
;; res_nmkquery(QUERY, www.sans.org, IN, A)
------------
SendRequest(), len 30
HEADER:
opcode = QUERY, id = 11862, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
www.sans.org, type = A, class = IN
------------
timeout
timeout
SendRequest failed
DNS definitely looks like it is suffering...
/nebulus
Works for me, was a little slow loading but it did load.
And this is what I get :
>While trying to retrieve the URL: http://www.sans.org/
>The following error was encountered:
>Unable to determine IP address from host name for www.sans.org
>The dnsserver returned:
>Name Error: The domain name does not exist.
>This means that:
> The cache was not able to resolve the hostname presented in the URL.
> Check if the address is correct.
Something might be wrong.
I am thinking that are updating the content(good thought) but they could also be being hit with alot of requests and it brought the server down hope it comes back up soon.
nebulus200 - heh, I got that same spam from them. It's just something about their webcast this coming Friday. Nothing about problems with the site or DNS.
FWIW I also cannot get to it from either our west coast or east coast locations. I get an unresolvable address.
I am getting there fine, no problems at all. :S
Yeah i was able to get to it too. But it was a bit slow.
PeacE
-BoB
according to one of the lists I'm on it looks like maybe register.com lost their databases for one reason or another. Here is a cut-n-paste from the list:
Quote:
>gtld's can't seem to point an NS to these domains:
>
>[root@mrtg mrtg]# nslookup
>> server k.gtld-servers.net
>Default server: k.gtld-servers.net
>Address: 192.52.178.30#53
>> set querytype=NS
>> sans.org
>Server: k.gtld-servers.net
>Address: 192.52.178.30#53
>
>Non-authoritative answer:
>*** Can't find sans.org: No answer
This is ... rather normal. .org is served by *.NSTLD.COM now. .net and .com
are still served by *.gtld-servers.net.
It looks like register.com either hosed their database, or hosed records
while trying to update various records (at the request of the owners or
someone else, who knows).
A variety of domains appear affected, sans.org, dhsield.org, incidents.org,
homepc.org, etc. All .org, all related and sharing infrastructure
aooerently.
Right now I'm inclined towards Occam's razor, this is a technical screw
up/"normal" DNS modification and not something "evil".