Or, the value of not using a free DNS service with (likely) no SLA for seemingly “critical” services. Good DNS services are relatively cheap in the grand scheme of things.
On Jul 4, 2024, at 3:52 PM, Crist Clark <cjc+na...@pumpky.net> wrote: On the other side of this, we all may be learning the value of not having all of you NS records in a single zone with a domain under a single registrar. (From someone who has personal domains hosted on HE DNS.) On Thu, Jul 4, 2024 at 1:01 PM Mel Beckman <m...@beckman.org<mailto:m...@beckman.org>> wrote: Aha. Just as I suspected, bureaucrats at Network Solutions are to blame. I have had many run-ins with NS and their inscrutable policies and odd viewpoints. I was once suspended for running a web cache that NS incorrectly claimed was stealing domain content. No engineer on the NS side seemed to know what a web cache does. -mel via cell On Jul 4, 2024, at 12:42 PM, Mel Beckman <m...@beckman.org<mailto:m...@beckman.org>> wrote: Ryan, Right you are. The dig still fails. hopefully the ICANN issue gets fixed, and a pox on any bureaucrat who arranged for this to happen over a holiday weekend! -mel On Jul 4, 2024, at 12:33 PM, Ryan Hamel <r...@rkhtech.org<mailto:r...@rkhtech.org>> wrote: Mel, Your local caching resolver knows the IPs for ns[1-5].he.net<http://he.net/>, which skips over the need for querying the root DNS resolvers, and gtld-servers (glue records). If the TTL (2 days) expires on your resolver before HE fixes their issue, you will not be able to resolve anything for that domain. At the moment, a simple DNS trace (dig he.net<http://he.net/> +trace) cannot complete fully. Ryan Hamel ________________________________ From: Mel Beckman <m...@beckman.org<mailto:m...@beckman.org>> Sent: Thursday, July 4, 2024 12:20 PM To: Jay Ashworth <j...@baylink.com<mailto:j...@baylink.com>> Cc: Ryan Hamel <r...@rkhtech.org<mailto:r...@rkhtech.org>>; nanog@nanog.org<mailto:nanog@nanog.org> <nanog@nanog.org<mailto:nanog@nanog.org>> Subject: Re: HE.net problem Caution: This is an external email and may be malicious. Please take care when clicking links or opening attachments. Our he.net<http://he.net/> dns appears to be fine at this time: $ nslookup server ns1.he.net<http://ns1.he.net/> Default server: ns1.he.net<http://ns1.he.net/> Address: 2001:470:100::2#53 Default server: ns1.he.net<http://ns1.he.net/> Address: 216.218.130.2#53 > set type=A > jet.net<http://jet.net/>. Server: ns1.he.net<http://ns1.he.net/> Address: 216.218.130.2#53 Name: jet.net<http://jet.net/> Address: 206.83.0.42 -mel beckman On Jul 4, 2024, at 12:11 PM, Jay Ashworth <j...@baylink.com<mailto:j...@baylink.com>> wrote: Cool, thanks. We had a couple of other reports of people making support calls and being asked to reboot their modems, so I wanted to make sure tier 3 had gotten it. And I figured tier 3 would be here. :-) Cheers, -- jra On July 4, 2024 3:00:12 PM EDT, Ryan Hamel <r...@rkhtech.org<mailto:r...@rkhtech.org>> wrote: I called their support when that outage thread came in, they're already aware and taking a look now. Ryan Hamel ________________________________ From: NANOG <nanog-bounces+ryan=rkhtech....@nanog.org<mailto:rkhtech....@nanog.org>> on behalf of Jay Ashworth <j...@baylink.com<mailto:j...@baylink.com>> Sent: Thursday, July 4, 2024 11:55 AM To: nanog@nanog.org<mailto:nanog@nanog.org> <nanog@nanog.org<mailto:nanog@nanog.org>> Subject: HE.net problem Caution: This is an external email and may be malicious. Please take care when clicking links or opening attachments. We have a report on outages that he.net<http://he.net/> has been placed in ICANN client hold, and people's DNS service is falling over on this Independence day. If you work in DNS for HE, you might want to look into this. I have double checked the report, and I am seeing the status as well. Hurricane serves lots of dns, I would classify this as a P1 ticket. Cheers, -- jra -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
