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".