full-disclosure - sans.org

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <002f01c371b0$05397420$1500020a@bigdog>
From: listuser at seifried.org (Kurt Seifried)
Subject: sans.org

>gtld's can't seem to point an NS to these domains:
>
>[root@...g 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".

Kurt Seifried, kurt@...fried.org
A15B BEE5 B391 B9AD B0EF
AEB0 AD63 0B4E AD56 E574
http://seifried.org/security/