<html><head></head><body><div dir="auto">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.</div><br><br><div class="gmail_quote"><div dir="auto">On July 4, 2024 2:48:54 PM EDT, "Michael B. Williams" <Michael.Williams@glexia.com> wrote:</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="auto">I also called and they said there are no issues and asked me to restart my modem and router? Ok…<br clear="all"><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">Sent from Gmail Mobile</div></div></div><div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jul 5, 2024 at 04:47 Tom Hek <<a href="mailto:tom@tomhek.net">tom@tomhek.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><u></u><div><div>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. :)<br></div><div><br></div><div>Kind regards,<br></div><div><br></div><div>Tom</div></div><div><div><br></div><div>On Thu, 4 Jul 2024, at 20:42, Michael B. Williams wrote:<br></div><blockquote type="cite" id="m_-4910239079353088197qt"><div dir="auto">Outages discussion<br></div><div dir="auto"><br></div><div dir="auto"><div>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…<br></div><div><br></div><div><div dir="ltr">Sent from Gmail Mobile<br></div></div></div><div><br></div><div><div><br></div><div><div dir="ltr">On Fri, Jul 5, 2024 at 04:41 Jay Ashworth <<a href="mailto:jra@baylink.com" target="_blank">jra@baylink.com</a>> wrote:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div><div dir="auto"><div>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. <br></div><div><br></div><div>Any further commentary that does not involve an he employee should move over to -discuss.<br></div></div></div><div><div><br></div><div><br></div><div><div dir="auto">On July 4, 2024 2:34:59 PM EDT, "Michael B. Williams via Outages" <<a href="mailto:outages@outages.org" target="_blank">outages@outages.org</a>> wrote:<br></div><blockquote style="margin:0pt 0pt 0pt 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div dir="auto"><div><div><p dir="auto">I’m seeing the same issues. <br></p><p dir="auto">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.<br></p></div></div><div>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?<br></div><div><br></div><div><div dir="ltr">Sent from Gmail Mobile<br></div></div></div><div><br></div><div><div><br></div><div><div dir="ltr">On Fri, Jul 5, 2024 at 04:28 Tom Hek via Outages <<a href="mailto:outages@outages.org" target="_blank">outages@outages.org</a>> wrote:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div><u></u><br></div><div><div>Hello Outages,<br></div><div><br></div><div>Seeing a bunch of resolution failures on our resolvers, after diagnosis I tracked it down to HE.net being in clientHold:<br></div><div><br></div><div> Domain Name: <a href="http://HE.NET" target="_blank">HE.NET</a><br></div><div> Registry Domain ID: 486609_DOMAIN_NET-VRSN<br></div><div> Registrar WHOIS Server: <a href="http://whois.networksolutions.com" target="_blank">whois.networksolutions.com</a><br></div><div> Registrar URL: <a href="http://networksolutions.com" target="_blank">http://networksolutions.com</a><br></div><div> Updated Date: 2024-07-04T15:06:46Z<br></div><div> Creation Date: 1995-07-31T04:00:00Z<br></div><div> Registry Expiry Date: 2033-07-30T04:00:00Z<br></div><div> Registrar: Network Solutions, LLC<br></div><div> Registrar IANA ID: 2<br></div><div> Registrar Abuse Contact Email: <a href="mailto:domain.operations@web.com" target="_blank">domain.operations@web.com</a><br></div><div> Registrar Abuse Contact Phone: +1.8777228662<br></div><div> Domain Status: clientHold <a href="https://icann.org/epp#clientHold" target="_blank">https://icann.org/epp#clientHold</a><br></div><div> Domain Status: clientTransferProhibited <a href="https://icann.org/epp#clientTransferProhibited" target="_blank">https://icann.org/epp#clientTransferProhibited</a><br></div><div> Name Server: <a href="http://NS1.HE.NET" target="_blank">NS1.HE.NET</a><br></div><div> Name Server: <a href="http://NS2.HE.NET" target="_blank">NS2.HE.NET</a><br></div><div> Name Server: <a href="http://NS3.HE.NET" target="_blank">NS3.HE.NET</a><br></div><div> Name Server: <a href="http://NS4.HE.NET" target="_blank">NS4.HE.NET</a><br></div><div> Name Server: <a href="http://NS5.HE.NET" target="_blank">NS5.HE.NET</a><br></div><div> DNSSEC: unsigned<br></div><div> URL of the ICANN Whois Inaccuracy Complaint Form: <a href="https://www.icann.org/wicf/" target="_blank">https://www.icann.org/wicf/</a><br></div><div>>>> Last update of whois database: 2024-07-04T18:19:09Z <<<<br></div><div><br></div><div><a href="http://ns1-5.he.net" target="_blank">ns1-5.he.net</a> 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.<br></div><div><br></div><div>Kind regards,<br></div><div><br></div><div>Tom Hek<br></div></div><div>_______________________________________________<br></div><div> Outages mailing list<br></div><div> <a href="mailto:Outages@outages.org" target="_blank">Outages@outages.org</a><br></div><div> <a href="https://puck.nether.net/mailman/listinfo/outages" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br></div></blockquote></div></div></blockquote></div><div dir="auto"><div><div>-- <br></div><div>Sent from my Android device with K-9 Mail. Please excuse my brevity.<br></div></div></div></div></blockquote></div></div></blockquote><div><br></div></div></blockquote></div></div>
</blockquote></div><div dir="auto"><div class='k9mail-signature'>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.</div></div></body></html>