named.root (was: Yay! AAAA records added for root servers)

Mailman List Mirror (Read Only)
1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Shame its not made it to HTTP yet:

$ lynx --source http://www.internic.net/zones/named.root | grep A | wc -l
~ 17
$ lynx --source http://www.internic.net/zones/named.root | grep AAAA | wc -l
~ 0

$ lynx --source http://www.internic.net/zones/named.root | grep "last
update"
; last update: Nov 01, 2007

vs

$ lynx --source ftp://rs.internic.net/domain/named.root | grep AAAA | wc -l
~ 6

$ lynx --source ftp://rs.internic.net/domain/named.root | grep "last update"

; last update: Feb 04, 2008

Apologies for the crosspost

Dave.

Mike Leber wrote:

For anybody that hasn't already seen this, a note of celebration is in
order. Hurrah!

dig @f.root-servers.net ns . +bufsize=1280

; <<>> DiG 9.3.4 <<>> @f.root-servers.net ns . +bufsize=1280
; (2 servers found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24611
;; flags: qr aa rd; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 20

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;. IN NS

;; ANSWER SECTION:
. 518400 IN NS K.ROOT-SERVERS.NET.
. 518400 IN NS L.ROOT-SERVERS.NET.
. 518400 IN NS M.ROOT-SERVERS.NET.
. 518400 IN NS A.ROOT-SERVERS.NET.
. 518400 IN NS B.ROOT-SERVERS.NET.
. 518400 IN NS C.ROOT-SERVERS.NET.
. 518400 IN NS D.ROOT-SERVERS.NET.
. 518400 IN NS E.ROOT-SERVERS.NET.
. 518400 IN NS F.ROOT-SERVERS.NET.
. 518400 IN NS G.ROOT-SERVERS.NET.
. 518400 IN NS H.ROOT-SERVERS.NET.
. 518400 IN NS I.ROOT-SERVERS.NET.
. 518400 IN NS J.ROOT-SERVERS.NET.

;; ADDITIONAL SECTION:
A.ROOT-SERVERS.NET. 3600000 IN A 198.41.0.4
A.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:503:ba3e::2:30
B.ROOT-SERVERS.NET. 3600000 IN A 192.228.79.201
C.ROOT-SERVERS.NET. 3600000 IN A 192.33.4.12
D.ROOT-SERVERS.NET. 3600000 IN A 128.8.10.90
E.ROOT-SERVERS.NET. 3600000 IN A 192.203.230.10
F.ROOT-SERVERS.NET. 3600000 IN A 192.5.5.241
F.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:500:2f::f
G.ROOT-SERVERS.NET. 3600000 IN A 192.112.36.4
H.ROOT-SERVERS.NET. 3600000 IN A 128.63.2.53
H.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:500:1::803f:235
I.ROOT-SERVERS.NET. 3600000 IN A 192.36.148.17
J.ROOT-SERVERS.NET. 3600000 IN A 192.58.128.30
J.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:503:c27::2:30
K.ROOT-SERVERS.NET. 3600000 IN A 193.0.14.129
K.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:7fd::1
L.ROOT-SERVERS.NET. 3600000 IN A 199.7.83.42
M.ROOT-SERVERS.NET. 3600000 IN A 202.12.27.33
M.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:dc3::35

;; Query time: 2 msec
;; SERVER: 2001:500:2f::f#53(2001:500:2f::f)
;; WHEN: Mon Feb 4 20:47:08 2008
;; MSG SIZE rcvd: 615

+----------------- H U R R I C A N E - E L E C T R I C -----------------+
> Mike Leber Wholesale IPv4 and IPv6 Transit 510 580 4100 |
> Hurricane Electric Web Hosting Colocation AS6939 |
> mleber@he.net http://he.net |
+-----------------------------------------------------------------------+

- --
David Freedman
Group Network Engineering
Claranet Limited

2

a message of 114 lines which said:

Shame its not made it to HTTP yet:

Nothing to do with the protocol but with the organization which
manages the server:

$ lynx --source http://www.internic.net/zones/named.root | grep AAAA

www.internic.net is managed by ICANN.

$ lynx --source ftp://rs.internic.net/domain/named.root | grep "last update"

rs.internic.net is managed by Verisign.

3

Well gosh, and there was me thinking that both would work together to make such a change :slight_smile:

And there is http://www.root-servers.org/ suggesting

"
The root hints file (named.cache, root.ca, root.hints, ...) can be obtained via IANA's page for popular links (http://www.iana.org/popular.htm)
"
which in turn points to [www|ftp].internic.net

....

Stephane Bortzmeyer wrote:

4

a message of 33 lines which said:

Well gosh, and there was me thinking that both would work together
to make such a change :slight_smile:

ICANN is typically 2-3 days behind the root zone file editor.

5

Hi,

There is a nightly cron job on ftp.internic.net that mirrors ftp.rs.internic.net.

Said cron job was failing, likely due to the maximum number of connections limit being reached on ftp.rs.internic.net.

Folks at VeriSign said they would be temporarily raising said limit.

You will note that the the hints file on ftp.internic.net is now correct.

Sorry for any confusion this might have caused.

Regards,
-drc

6

Hi,

In the case of root zone file edits, IANA does not post completion until we
are notified by VeriSign that the change is complete. This typically lags a
few days from when the change actually enters the zone file. This is an
issue we have raised with VeriSign on several occasions and should be
remedied for good in the near future with the deployment of new software to
help manage the root zone data.

This is completely independent of the fact that a mirror failed because a
maximum connection limit was being reached.

Thanks,
-drc