[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Dnssec still inoperable on the internet ?— was ARIN NS down?

Subject: Dnssec still inoperable on the internet ?— was ARIN NS down?
From: cb.list6 at gmail.com (Ca By)
Date: Fri, 11 Jan 2019 07:58:25 -0800
In-reply-to: <[email protected]>
References: <[email protected]> <[email protected]>

Thanks for the update that dnssec STILL causes more real world problems
than it solves.

.....

That said, arin is a pro outfit. If they can screw it up, like nasa, so can
you. No your threats and deploy wisely

---------- Forwarded message ---------
From: John Curran <jcurran at istaff.org>
Date: Fri, Jan 11, 2019 at 6:36 AM
Subject: Re: ARIN NS down?
To: Suresh Ramasubramanian <ops.lists at gmail.com>
CC: NANOG <nanog at nanog.org>


Suresh -

Weâ??re aware and working the problem.  It looks to me like expired
RRSIG/DNSKEYâ??s for the zone,
so if youâ??re using a DNSSEC validating resolver (e.g. Google, Cloudflare,
Cogent) then ARIN.NET <http://arin.net/>
is unreachable.   ARINâ??s engineering team is working on resolution now.

/John

John Curran
President and CEO
American Registry for Internet Numbers


On 11 Jan 2019, at 9:27 AM, Suresh Ramasubramanian <ops.lists at gmail.com>
wrote:

couldn't get address for 'ns1.arin.net': not found
couldn't get address for 'ns2.arin.net': not found
couldn't get address for 'u.arin.net': not found
couldn't get address for 'ns3.arin.net': not found
dig: couldn't get address for 'ns1.arin.net': no more

srs at Sureshs-MacBook-Pro-2 19:56:18 <~> $ dig +trace +norec whois.arin.net

; <<>> DiG 9.10.6 <<>> +trace +norec whois.arin.net
;; global options: +cmd
. 2230 IN NS m.root-servers.net.
. 2230 IN NS b.root-servers.net.
. 2230 IN NS c.root-servers.net.
. 2230 IN NS d.root-servers.net.
. 2230 IN NS e.root-servers.net.
. 2230 IN NS f.root-servers.net.
. 2230 IN NS g.root-servers.net.
. 2230 IN NS h.root-servers.net.
. 2230 IN NS i.root-servers.net.
. 2230 IN NS j.root-servers.net.
. 2230 IN NS a.root-servers.net.
. 2230 IN NS k.root-servers.net.
. 2230 IN NS l.root-servers.net.
. 2230 IN RRSIG NS 8 0 518400 20190121050000 20190108040000 16749 .
JqXTRb0qik0Iy1zDpwKRfKr1iZjTeiJRTk1GCfIWh9dFFvhN0c7Fiz6H
lbNfhgQbPsacG0b/1I3rguS13H2guX7apppK2w88h+z8mzym2Bw1C1HR
ZR3ocj/jHLJbMqHdQ+DFyRdw/AxCXBdhnbX46C8+unhQ03D/MzS0M0t4
vgadYi7BN4sa+iZIilwFV56n2dOfpzyO+evVbcnTLRZ6D4bjCHZLCtO8
EDziAPUbVAPZWiflb7/Y2dECe5gbOuGYYU/xv/Pal5+v9cjgMjcf8buG
S+iTIL/lnus0JJSRDmkM6yzfYMBXC2ZqhOp+Ls+EfvmqFjIZzi394XCi pdKRZw==
;; Received 525 bytes from 10.0.0.1#53(10.0.0.1) in 40 ms

net. 172800 IN NS g.gtld-servers.net.
net. 172800 IN NS c.gtld-servers.net.
net. 172800 IN NS j.gtld-servers.net.
net. 172800 IN NS e.gtld-servers.net.
net. 172800 IN NS h.gtld-servers.net.
net. 172800 IN NS k.gtld-servers.net.
net. 172800 IN NS m.gtld-servers.net.
net. 172800 IN NS i.gtld-servers.net.
net. 172800 IN NS f.gtld-servers.net.
net. 172800 IN NS b.gtld-servers.net.
net. 172800 IN NS a.gtld-servers.net.
net. 172800 IN NS d.gtld-servers.net.
net. 172800 IN NS l.gtld-servers.net.
net. 86400 IN DS 35886 8 2
7862B27F5F516EBE19680444D4CE5E762981931842C465F00236401D 8BD973EE
net. 86400 IN RRSIG DS 8 1 86400 20190124130000 20190111120000 16749 .
uahpltN27UkKaFJRaAU1on+IpC2lpgZo84XEM7Pk7dQysKfSnqUkaVLY
PXQf9kvgW5eOx/+BttQB2OWFLckJs8vv5ScOpz7dDhs8zR2FPLm93HTD
4F/XEKDNOQbFGSA3g4pZq3fatY7kFEkV9sFTH90WqJt0sXe64LYFcwr2
FtrJaS/yhEV4XDbsN3RLkBP58bf526LPpvonwSZsMUTDZcnXtUnc57ZI
dlTHg2snNhVWu4qJfHDsEQPwOZagRXJhjlRT8Ox/7HwXvplmRfmeuhZb
Vj5kdiY+3j0RTxpLRCG/SZRDIRcvdFKh9umdwQvAzuTS0xzO8OyPw9q8 8QCCYg==
;; Received 1171 bytes from 192.112.36.4#53(g.root-servers.net) in 207 ms

arin.net. 172800 IN NS ns1.arin.net.
arin.net. 172800 IN NS ns2.arin.net.
arin.net. 172800 IN NS u.arin.net.
arin.net. 172800 IN NS ns3.arin.net.
arin.net. 86400 IN DS 48281 5 2
6EB0CCF325A8101A768C93D10CE084303D3714D4E92FEE53D6E683D2 22291017
arin.net. 86400 IN DS 48281 5 1 FCBF93357C8FE3247CECB2CD277F45EB955EE4CE
arin.net. 86400 IN RRSIG DS 8 2 86400 20190117062448 20190110051448 6140
net. stuWyfC0PDuk2hNF/Bnz0lnypk+bA/slTa2KYznjmoLXDtq7v1obJq41
ZfloQKXuC7MnzpCQj70GU9ZESZq1/XU+u6wDmCqmEUbJ3kyrILxkVrln
bTEySJWPmurpwUVzDVfvqFpXEOhWxOjDu6drZMcC3wG9EdPqBuFC6wlf FIQ=
couldn't get address for 'ns1.arin.net': not found
couldn't get address for 'ns2.arin.net': not found
couldn't get address for 'u.arin.net': not found
couldn't get address for 'ns3.arin.net': not found
dig: couldn't get address for 'ns1.arin.net': no more
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190111/36db18cd/attachment.html>

Follow-Ups:
- Dnssec still inoperable on the internet ?— was ARIN NS down?
  - From: bortzmeyer at nic.fr (Stephane Bortzmeyer)
- Re: Dnssec still inoperable on the internet ?— was ARIN NS down?
  - From: maxtul at netassist.ua (Max Tulyev)
- Re: Dnssec still inoperable on the internet ?— was ARIN NS down?
  - From: swmike at swm.pp.se (Mikael Abrahamsson)

References:
- ARIN NS down?
  - From: ops.lists at gmail.com (Suresh Ramasubramanian)
- ARIN NS down?
  - From: jcurran at istaff.org (John Curran)

Prev by Date: ARIN NS down?
Next by Date: Dnssec still inoperable on the internet ?— was ARIN NS down?
Previous by thread: ARIN NS down?
Next by thread: Dnssec still inoperable on the internet ?— was ARIN NS down?
Index(es):
- Date
- Thread