>> what foss dns monitoring tools do folk use to alert of
>> - iminent delegation expiry
>> - inconsistent service (lame, soa mismatches, ...)
>> - dnssec signing and timer issues
>> - etc.
> https://github.com/berthubert/simplomon
thanks. may play
hak whacked me to add
http://dns.measur
On Fri, 5 Jul 2024 at 06:59, Randy Bush wrote:
> not to distract from everyone diagnosing someone else's problem, but ...
>
> what foss dns monitoring tools do folk use to alert of
> - iminent delegation expiry
> - inconsistent service (lame, soa mismatches, ...)
> - dnssec signing and time
http://www.rfc-editor.org/rfc/rfc2182.txtIs what you should use as guidance Sent via RFC1925 compliant deviceOn Jul 4, 2024, at 4:55 PM, Crist Clark 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
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 wrote:
On the other side of this, we all may be learning the value of not having a
> On 4 Jul 2024, at 21:53, Crist Clark 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.
The majority of real large DNS hosting providers have their authoritative under
mul
not to distract from everyone diagnosing someone else's problem, but ...
what foss dns monitoring tools do folk use to alert of
- iminent delegation expiry
- inconsistent service (lame, soa mismatches, ...)
- dnssec signing and timer issues
- etc.
randy
After a metric ton of screaming, we did get the issue solved. Thanks
everyone, and we WILL be following up with the powers that be.
Reid
On Thu, Jul 4, 2024, 3:31 PM Reid Fishler wrote:
> Network Solutions has decided to put our domain name on Client Hold due to
> a single phishing complaint ab
cjc> On the other side of this, we all may be learning the value of not
cjc> having all of you NS records in a single zone with a domain under a
cjc> single registrar.
>From some trainings I did on how to be sure your DNS was robust:
- don't have all your business critical domains under the sam
It appears that Reid Fishler via NANOG said:
>-=-=-=-=-=-
>
>Network Solutions has decided to put our domain name on Client Hold due to
>a single phishing complaint about a web page, which happens to just be a
>page of information about another domain from bgp.he.net. Network Solutions
>has been c
Yup; I blew that one too.
I've been told it was cleared around 2020Z, and whois reflects that,
though my dig +trace doesn't seem to be behaving as expected.
Cheers,
-- jra
- Original Message -
> From: "Crist Clark"
> To: "Mel Beckman"
> Cc: nanog@nanog.org
> Sent: Thursday, July 4, 20
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 wrote:
> Aha. Just as I suspected, burea
jra> We have a report on outages that he.net has been placed in ICANN
jra> client hold, and people's DNS service is falling over on this
jra> Independence day.
Seems to have had hold removed 20:20 zulu, according to whois.
Domain back in .net and working again.
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 k
Network Solutions has decided to put our domain name on Client Hold due to
a single phishing complaint about a web page, which happens to just be a
page of information about another domain from bgp.he.net. Network Solutions
has been contacted, and refuses to handle this issue in ANY expedited
manne
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 wrote:
Mel,
Your local caching resolver knows the IPs for ns[1-5].he.net, which
Mel,
Your local caching resolver knows the IPs for ns[1-5].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.
I've been informed that the CEO of HE is on this as of 1512EDT.
I approve of the scale of this response. :-)
Cheers,
-- jra
On July 4, 2024 2:55:34 PM EDT, Jay Ashworth wrote:
>We have a report on outages that he.net has been placed in ICANN client hold,
>and people's DNS service is falling ov
Our he.net dns appears to be fine at this time:
$ nslookup
server ns1.he.net
Default server: ns1.he.net
Address: 2001:470:100::2#53
Default server: ns1.he.net
Address: 216.218.130.2#53
> set type=A
> jet.net.
Server: ns1.he.net
Address:216.218.130.2#53
Name: jet.net
Address: 206
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 wrote:
>I called their suppor
I called their support when that outage thread came in, they're already aware
and taking a look now.
Ryan Hamel
From: NANOG on behalf of Jay
Ashworth
Sent: Thursday, July 4, 2024 11:55 AM
To: nanog@nanog.org
Subject: HE.net problem
Caution: This is an extern
We have a report on outages that 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 lo
21 matches
Mail list logo
