Re: Advisory — D-root is changing its IPv4 address on the 3rd of January.
Concomittant wirh reduced risk assessment capability? Sent from Samsung Mobile -------- Original message -------- From: Randy Bush <randy@psg.com> Date: To: Lynda <shrdlu@deaddrop.org> Cc: North American Network Operators' Group <nanog@nanog.org> Subject: Re: Advisory — D-root is changing its IPv4 address on the 3rd of January.
For anyone who is worried that the root server change might impact them, they can go to http://www.iana.org/domains/root/files and download the root zone file. It probably won't need to be updated again until the next round of gTLDs is approved. ----------------------------------------------------------------------------------------------- -ITG (ITechGeek) ITG@ITechGeek.Com https://itg.nu/ GPG Keys: https://itg.nu/contact/gpg-key Preferred GPG Key: Key ID: DCB1191A / Fingerprint: AB46B7E363DA7E04ABFA57852AA9910ADCB1191A Google Voice: +1-703-493-0128 / Twitter: ITechGeek / Facebook: http://fb.me/Jbwa.Net On Mon, Dec 17, 2012 at 8:53 PM, Keith Medcalf <kmedcalf@dessus.com> wrote:
Concomittant wirh reduced risk assessment capability?
Sent from Samsung Mobile
-------- Original message -------- From: Randy Bush <randy@psg.com> Date: To: Lynda <shrdlu@deaddrop.org> Cc: North American Network Operators' Group <nanog@nanog.org> Subject: Re: Advisory — D-root is changing its IPv4 address on the 3rd of January.
On Dec 17, 2012, at 11:30 PM, ITechGeek <itg@itechgeek.com> wrote:
For anyone who is worried that the root server change might impact them, they can go to http://www.iana.org/domains/root/files and download the root zone file. It probably won't need to be updated again until the next round of gTLDs is approved.
Err, no. The root zone changes twice a day and its contents change quite frequently as TLD managers update their name servers, do key rollovers, etc. If you're going to copy the root zone, I'd recommend using a zone transfer from the name servers described in http://dns.icann.org/services/axfr/ or, at the very least, set up a cron job to pull the root zone twice a day. WRT the root _hints_ change, setting up a cron job to pull, verify, and install the root hints file periodically (once a month should probably be sufficient) would probably be a good idea. Regards, -drc
On 2012-12-18, at 11:15, David Conrad <drc@virtualized.org> wrote:
WRT the root _hints_ change, setting up a cron job to pull, verify, and install the root hints file periodically (once a month should probably be sufficient) would probably be a good idea.
This change appears to have been completed, as of root zone serial 2013010300: [krill:~]% host d.root-servers.net d.root-servers.net has address 199.7.91.13 d.root-servers.net has IPv6 address 2001:500:2d::d [krill:~]% [krill:~]% curl -s ftp://rs.internic.net/domain/named.root | fgrep D.ROOT . 3600000 NS D.ROOT-SERVERS.NET. D.ROOT-SERVERS.NET. 3600000 A 199.7.91.13 D.ROOT-SERVERS.NET. 3600000 AAAA 2001:500:2D::D [krill:~]% The authoritative location of the root hints file is <ftp://rs.internic.net/domain/named.root> and those who feel like being tidy DNS admins could pull a fresh copy from there so that the next time their nameserver is restarted it will prime optimally. As discussed at some length before, those who prefer to be more hands-off about this will very likely see no negative impact from their laziness. Joe
On Jan 3, 2013, at 11:38 AM, Joe Abley wrote: On 2012-12-18, at 11:15, David Conrad <drc@virtualized.org> wrote:
WRT the root _hints_ change, setting up a cron job to pull, verify, and install the root hints file periodically (once a month should probably be sufficient) would probably be a good idea.
Perhaps someone at internic.net could explain why the file in the first directory is WRONG but that in the second includes the correct info? [legacy cron jobs pointing at FTP. will obviously not succeed] ; This file is made available by InterNIC ; under anonymous FTP as ; file /domain/named.cache ; on server FTP.INTERNIC.NET ; -OR- RS.INTERNIC.NET Regards -H-
Hi Henry, On 2013-01-03, at 13:29, Henry Steuart <HSteuart@alliedtelecom.net> wrote:
Perhaps someone at internic.net could explain why the file in the first directory is WRONG but that in the second includes the correct info? [legacy cron jobs pointing at FTP. will obviously not succeed]
; This file is made available by InterNIC ; under anonymous FTP as ; file /domain/named.cache ; on server FTP.INTERNIC.NET ; -OR- RS.INTERNIC.NET
I am not one of the people who works with root zone management, but I understand that: - the normative location of the root hints file is ftp://rs.internic.net/domain/named.root - some of the other mirrors take a few hours to update I appreciate that this is not obviously congruent with the text in the file you cited. I'll pass on this message, and thanks for the feedback. Joe
participants (5)
-
David Conrad -
Henry Steuart -
ITechGeek -
Joe Abley -
Keith Medcalf