5 ms·

Indeed was Domain Status: clientHold https://icann.org/epp#clientHold https://icann.org/epp#clientHold now Domain Status: clientTransferProhibited https://ica

Indeed was Domain Status: clientHold https://icann.org/epp#clientHold https://icann.org/epp#clientHold now Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited https://icann.org/epp#clientTransferProhibited Verified he.net is correctly listed in the root servers, though I did not check prior. dig +nocookie @i.gtld-servers.net he.net ;; AUTHORITY SECTION: he.net. 172800 IN NS ns1.he.net. he.net. 172800 IN NS ns2.he.net. he.net. 172800 IN NS ns3.he.net. he.net. 172800 IN NS ns4.he.net. he.net. 172800 IN NS ns5.he.net. ;; ADDITIONAL SECTION: ns1.he.net. 172800 IN AAAA 2001:470:100::2 ns1.he.net. 172800 IN A 216.218.130.2 ns2.he.net. 172800 IN AAAA 2001:470:200::2 ns2.he.net. 172800 IN A 216.218.131.2 ns3.he.net. 172800 IN AAAA 2001:470:300::2 ns3.he.net. 172800 IN A 216.218.132.2 ns4.he.net. 172800 IN AAAA 2001:470:400::2 ns4.he.net. 172800 IN A 216.66.1.2 ns5.he.net. 172800 IN AAAA 2001:470:500::2 ns5.he.net. 172800 IN A 216.66.80.18 which belong to Hurricane [1] [1] - https://bgp.he.net/AS6939#_whois https://bgp.he.net/AS6939#_whois

toast0 2y ago
I don't have a paste, but a similar query gave me NXDOMAIN during the incident. I did get the A/AAAA glue records for nsX.he.net when asking gtld-servers[1] about my .net, though. [1] note that these are tld servers run by Verisign, not root servers organized by ICANN or IANA and run by multiple organizations. A few decades ago, I think root-servers.net did do root and also the three letter tlds, but that was a long time ago, before everything got split up into multiple roles.
- LinuxBender 2y ago
  note that these are tld servers run by Verisign I have old habits I am trying to break doing things from memory as it gets me into trouble here for saying outdated things, so I just did 'dig -t ns net' and then did a dig @ the first one in the list. I considered checking them all but I don't know what the current convergence time in the anycast clusters are for net. I'm glad you caught the NXDOMAIN. It's really one more epoxy coated screw in the coffin proving people should move off that registrar. It should take a great deal more than an abuse complaint to get a domain on hold, especially one belonging to a large network provider. Maybe it would make sense at this time for Hurricane to become it's own registrar. I printed out the book of requirements. For a retired hobbyist like me it would be insane, but for a business I think they could do it without too much overhead.

toast0 2y ago

I don't have a paste, but a similar query gave me NXDOMAIN during the incident. I did get the A/AAAA glue records for nsX.he.net when asking gtld-servers[1] about my .net, though. [1] note that these are tld servers run by Verisign, not root servers organized by ICANN or IANA and run by multiple organizations. A few decades ago, I think root-servers.net did do root and also the three letter tlds, but that was a long time ago, before everything got split up into multiple roles.

LinuxBender 2y ago
note that these are tld servers run by Verisign I have old habits I am trying to break doing things from memory as it gets me into trouble here for saying outdated things, so I just did 'dig -t ns net' and then did a dig @ the first one in the list. I considered checking them all but I don't know what the current convergence time in the anycast clusters are for net. I'm glad you caught the NXDOMAIN. It's really one more epoxy coated screw in the coffin proving people should move off that registrar. It should take a great deal more than an abuse complaint to get a domain on hold, especially one belonging to a large network provider. Maybe it would make sense at this time for Hurricane to become it's own registrar. I printed out the book of requirements. For a retired hobbyist like me it would be insane, but for a business I think they could do it without too much overhead.