Send Outages-discussion mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/outages-discussion
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Outages-discussion digest..."
Today's Topics:
1. Re: Outage ns1-ns5.he.net, clientHold in WHOIS for he.net
(Michael B. Williams)
2. Re: Outage ns1-ns5.he.net, clientHold in WHOIS for he.net
(Jay Ashworth)
----------------------------------------------------------------------
Message: 1
Date: Fri, 5 Jul 2024 04:48:54 +1000
From: "Michael B. Williams" <[email protected]>
To: Tom Hek <[email protected]>
Cc: Jay Ashworth <[email protected]>, Outages Discussion
<[email protected]>
Subject: Re: [Outages-discussion] Outage ns1-ns5.he.net, clientHold in
WHOIS for he.net
Message-ID:
<CAGj=18hsuds7ryqvs_gmwlnz8baznrwhrnsbyjgdc_o1r4b...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
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 <[email protected]> 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 <[email protected]> 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" <
> [email protected]> 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 <[email protected]>
> 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: [email protected]
> 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
> [email protected]
> 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-0001.htm>
------------------------------
Message: 2
Date: Thu, 04 Jul 2024 14:57:52 -0400
From: Jay Ashworth <[email protected]>
To: "Michael B. Williams" <[email protected]>, Tom Hek
<[email protected]>
Cc: Outages Discussion <[email protected]>
Subject: Re: [Outages-discussion] Outage ns1-ns5.he.net, clientHold in
WHOIS for he.net
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Yeah, that's an eyeball customer support line. While I suspect HE has some
people on this list, I know they have people on NANOG, and I have just promoted
the report over there as a P1.
On July 4, 2024 2:48:54 PM EDT, "Michael B. Williams"
<[email protected]> wrote:
>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 <[email protected]> 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 <[email protected]> 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" <
>> [email protected]> 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 <[email protected]>
>> 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: [email protected]
>> 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
>> [email protected]
>> https://puck.nether.net/mailman/listinfo/outages
>>
>> --
>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>>
>>
>>
--
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/20240704/d2ba4915/attachment.htm>
------------------------------
Subject: Digest Footer
_______________________________________________
Outages-discussion mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/outages-discussion
------------------------------
End of Outages-discussion Digest, Vol 169, Issue 2
**************************************************