[Outages-discussion] Outage ns1-ns5.he.net, clientHold in WHOIS for he.net

Michael B. Williams Michael.Williams at glexia.com
Thu Jul 4 14:48:54 EDT 2024


I also called and they said there are no issues and asked me to restart my
modem and router? Ok…

Sent from Gmail Mobile


On Fri, Jul 5, 2024 at 04:47 Tom Hek <tom at tomhek.net> wrote:

> I tried to reach out to their support via phone, but the person picking up
> the phone said everything was working and didn't see a reason to create a
> ticket about it, even after trying to explain what the WHOIS status meant
> and that their main domain is currently not resolving. Well, I tried. :)
>
> Kind regards,
>
> Tom
>
> On Thu, 4 Jul 2024, at 20:42, Michael B. Williams wrote:
>
> Outages discussion
>
> The issue is they can’t even receive email right now so unless they have
> their personal email on here they might not know there is an issue. I also
> reached out on Twitter…
>
> Sent from Gmail Mobile
>
>
> On Fri, Jul 5, 2024 at 04:41 Jay Ashworth <jra at baylink.com> wrote:
>
> Hopefully somebody who actually works at Hurricane Electric will chime in
> fairly promptly, and let us restrain comment on this list to that actual
> thread.
>
> Any further commentary that does not involve an he employee should move
> over to -discuss.
>
>
> On July 4, 2024 2:34:59 PM EDT, "Michael B. Williams via Outages" <
> outages at outages.org> wrote:
>
> I’m seeing the same issues.
>
> For those who don’t know the clientHold status code tells a domain's
> registry to not activate a domain in the DNS and as a consequence, it will
> not resolve. It is an uncommon status that is usually enacted during legal
> disputes, non-payment, or when a domain is subject to deletion.
> Given the expiry of this domain is 2033 something else is going on… anyone
> have a contact at HE who could shead some light on this situation?
>
> Sent from Gmail Mobile
>
>
> On Fri, Jul 5, 2024 at 04:28 Tom Hek via Outages <outages at outages.org>
> wrote:
>
>
> Hello Outages,
>
> Seeing a bunch of resolution failures on our resolvers, after diagnosis I
> tracked it down to HE.net being in clientHold:
>
>    Domain Name: HE.NET
>    Registry Domain ID: 486609_DOMAIN_NET-VRSN
>    Registrar WHOIS Server: whois.networksolutions.com
>    Registrar URL: http://networksolutions.com
>    Updated Date: 2024-07-04T15:06:46Z
>    Creation Date: 1995-07-31T04:00:00Z
>    Registry Expiry Date: 2033-07-30T04:00:00Z
>    Registrar: Network Solutions, LLC
>    Registrar IANA ID: 2
>    Registrar Abuse Contact Email: domain.operations at web.com
>    Registrar Abuse Contact Phone: +1.8777228662
>    Domain Status: clientHold https://icann.org/epp#clientHold
>    Domain Status: clientTransferProhibited
> https://icann.org/epp#clientTransferProhibited
>    Name Server: NS1.HE.NET
>    Name Server: NS2.HE.NET
>    Name Server: NS3.HE.NET
>    Name Server: NS4.HE.NET
>    Name Server: NS5.HE.NET
>    DNSSEC: unsigned
>    URL of the ICANN Whois Inaccuracy Complaint Form:
> https://www.icann.org/wicf/
> >>> Last update of whois database: 2024-07-04T18:19:09Z <<<
>
> ns1-5.he.net stopped resolving due to this as HE.net disappeared from the
> .net zone, so all domains that use them as a authoritative DNS might stop
> resolving soon as well.
>
> Kind regards,
>
> Tom Hek
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages-discussion/attachments/20240705/a4d40c04/attachment.htm>


More information about the Outages-discussion mailing list