Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

HE.net problem

mailman.nanog.org

Post reply on HN
Print view View original

31–40 of 43 posts

Re: HE.net problem

#31

Post by basilgohar »

First off, Hurricane Electric has always been one of the "cool" companies on the Internet since the early days (of public Internet, at least). So, my goodwill with them tells me that Network Solutions, a company that most certainly has NOT been one of the cool companies, is at fault. I feel and know this to be the case now, as well.

Having said that, I am also greatly pleased that the NANOG mailing list is public and plebes like us can see these kinds of discussions, which I feel are becoming harder to find as time goes on as services get consolidated into larger, government-friendly corporate private digital gardens.

Re: HE.net problem

#33

Post by omoikane »

The hold appears to have been removed as of few minutes ago:

https://mailman.nanog.org/pipermail/nanog/2024-July/225903.h...

I didn't know HE.net was using Network Solutions, maybe they will switch to someone else soon. My personal experience with Network Solutions wasn't so great (lots of trouble and human intervention needed to transfer a domain out of their service).

Re: HE.net problem

#34

Post by a-dub »

bifrost wrote: post #30
a-dub wrote: post #27

Earlier quoted context omitted.

> Its not really going to affect their services, maybe email in/out of it but thats about it idk. how do you know that their management capability can run sans dns?

Because they run their own DNS servers and inside of their network they're going to be using their own infra...

idk. aren't they tier 1? what if it breaks peering? is all their management capability strictly "inside" their network? what would happen to the rest of the internet if they dropped off?

Re: HE.net problem

#35

Post by LinuxBender »

KennyBlanken wrote: post #21
codetrotter wrote: post #16

Status in whois response is “active” for me, and he.net resolves from DNS for me, so I guess it’s been fixed? But why did they list a @he.net email address as one of the emails to contact them on? Wasn’t the problem that he.net would not resolve because of that very client hold?

Confirmed at 3:30 CT

Indeed

was Domain Status: clientHold https://icann.org/epp#clientHold

now Domain Status: 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

Re: HE.net problem

#36

Post by toast0 »

LinuxBender wrote: post #35
KennyBlanken wrote: post #21

Earlier quoted context omitted.

Confirmed at 3:30 CT

Indeed was Domain Status: clientHold https://icann.org/epp#clientHold now Domain Status: 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. 17…

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.

Re: HE.net problem

#37

Post by killerstorm »

Reviving1514 wrote: post #14
killerstorm wrote: post #8

[flagged]

Please elaborate, how would block chain solve this problem?

There's a number of DNS-like protocols on blockchain, e.g. ENS (Ethereum Name System - https://ens.domains/), Handshake (https://handshake.org/).

They provide same functionality as DNS[sec]. You are not at whim of a corpo, nobody can suspend you, corrupting or hijacking records is pretty much impossible...

Re: HE.net problem

#39

Post by [deleted] »

basilgohar wrote: post #31

First off, Hurricane Electric has always been one of the "cool" companies on the Internet since the early days (of public Internet, at least). So, my goodwill with them tells me that Network Solutions, a company that most certainly has NOT been one of the cool companies, is at fault. I feel and know this to be the case now, as well. Having said that, I am also greatly pleased that the NANOG mailing list is public and…

[deleted]

Re: HE.net problem

#40

Post by LinuxBender »

toast0 wrote: post #36
LinuxBender wrote: post #35

Earlier quoted context omitted.

Indeed was Domain Status: clientHold https://icann.org/epp#clientHold now Domain Status: 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. 17…

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…

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.

Post reply on HN