Bender
6 hours ago
World wide it appears [1]. I get NXDOMAIN from the .net root servers. Domain registration status appears normal.
From the github thread:
Indeed, if you do dig @ns3.inwx.de newpipe.net you will get a proper response, but other nameservers have not yet picked up on the registrar change
Someone did the migration wrong as the root servers have no glue records for anyone to boot-strap from.
dig @192.54.112.30 newpipe.net -t ns # one of the .net root servers
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN
sybercecurity
6 hours ago
I doubt that the .net TLD pulled the registration on purpose. WHOIS claims it was registered yesterday. Unless the TLD had some sort of hickup and reverted back to a version before it was registered. Or something on the registrar end that made it a parked domain instead of live.
Or someone got the registration pulled for some reason. Check your registrar portal.
Bender
6 hours ago
Ya I think someone or something borked up the migration. The glue records are missing in the .net root servers and someone added a comment to the github thread. They need to add the glue records ASAP. They should have first created the records in the new name servers and then changed the glue records rather than remove them.
Edit: (17:57 UTC) Still no glue records. They should get on the phone with their registrar.
They closed the git issue talking about DNSSEC keys but there are still no glue records. /shrug back to a video game for me.