On Thu 04 Jul 2024 18:16:28 GMT, Randy Bush wrote:
> hak whacked me to add
> http://dns.measurement-factory.com/tools/nagios-plugins/check_zone_rrsig_expiration.html
> to my nagios deployment.
>
> anyone have some known sick in various ways dns zones against which to
> test?
Those domains are bro
>> 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
.
Ryan Hamel
From: Mel Beckman <m...@beckman.org>
Sent: Thursday, July 4, 2024 12:20 PM
To: Jay Ashworth <j...@baylink.com>
Cc: Ryan Hamel <r...@rkhtech.org>; nanog@nanog.org <nanog@nanog.org>
Subject: Re: HE.net problem
Caution: This is an external em
aylink.com>>
Cc: Ryan Hamel mailto:r...@rkhtech.org>>;
nanog@nanog.org<mailto: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.
Ou
> 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
anog@nanog.org
> Sent: Thursday, July 4, 2024 4:52:14 PM
> Subject: Re: HE.net problem
> 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
*Sent:* Thursday, July 4, 2024 12:20 PM
> *To:* Jay Ashworth
> *Cc:* Ryan Hamel ; 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 dns a
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.
anything for that domain.
At the moment, a simple DNS trace (dig he.net +trace) cannot complete fully.
Ryan Hamel
From: Mel Beckman
Sent: Thursday, July 4, 2024 12:20 PM
To: Jay Ashworth
Cc: Ryan Hamel ; nanog@nanog.org
Subject: Re: HE.net problem
Caution: This is
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
fully.
Ryan Hamel
From: Mel Beckman
Sent: Thursday, July 4, 2024 12:20 PM
To: Jay Ashworth
Cc: Ryan Hamel ; 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
.
At the moment, a simple DNS trace (dig he.net +trace) cannot complete fully.
Ryan Hamel
From: Mel Beckman
Sent: Thursday, July 4, 2024 12:20 PM
To: Jay Ashworth
Cc: Ryan Hamel ; nanog@nanog.org
Subject: Re: HE.net problem
Caution: This is an external email
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
21 matches
Mail list logo
