[dns-operations] AAAA record for c.root-servers.net

[Stephan Lagerholm]

Hi DNS-ops,

c.root-servers.net is not reachable over v6 for everybody. There appears to be some peering disputes between operators over v6 still. Additionally, Leen Besselink told me on another mailing list (unbound) that it is advertized as a /48 that might get filtered.

What are the reachability requirements before something gets added to the root zone?

I'm not sure what is right or wrong here and the train already left the station, but I wanted to start a discussion if it was wise to add this into the root-zone at this point?

Thanks, Stephan


> -----Original Message-----
> From: dns-operations-bounces at lists.dns-oarc.net [mailto:dns-operations-
> bounces at lists.dns-oarc.net] On Behalf Of Weinberg, Matt
> Sent: Friday, March 28, 2014 1:57 PM
> To: dns-operations at dns-oarc.net
> Subject: Re: [dns-operations] AAAA record for c.root-servers.net
> 
> We¹ve corrected the update issue and subsequently fixed the ³last
> update² field.  The latest files are available on the rs.internic.net
> servers (for example, ftp://rs.internic.net/domain/named.root).
> 
> Joe is right < http://www.internic.net/domain/named.root is maintained
> by ICANN.  I believe that ICANN pulls updates from rs.internic.net on a
> scheduled basis.  We¹re following up with ICANN to confirm.
> 
> Thanks,
> Matt
> 
> 
> 
> On 3/28/14, 2:28 PM, "Joe Abley" <jabley at hopcount.ca> wrote:
> 
> >
> >On 28 Mar 2014, at 13:16, Anthony Kirby <Anthony.Kirby at nominet.org.uk>
> >wrote:
> >
> >> the copy available at ftp://rs.internic.net/domain/ does contain the
> >>AAAA, although that at ftp.internic.net does not;  that's the only
> >>diff, & both say "last update Jan 3 2013".
> >
> >I think rs is run by Verisign and ftp is run by ICANN, and ftp mirrors
> >from rs. Kim Davies is on this list and will surely react in due
> >course, but I'm guessing he's in transit between Singapore and LA
> right
> >now following the ICANN meeting this week.
> >
> >Might be just a matter of waiting for a nightly cron job.
> >
> >If I'm right about the data flow, then the "Jan 3 2013" thing is
> >presumably something for Verisign to clean up (if they haven't
> already).
> >
> >
> >Joe
> >_______________________________________________
> >dns-operations mailing list
> >dns-operations at lists.dns-oarc.net
> >https://lists.dns-oarc.net/mailman/listinfo/dns-operations
> >dns-jobs mailing list
> >https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
> 
> _______________________________________________
> dns-operations mailing list
> dns-operations at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/dns-operations
> dns-jobs mailing list
> https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
> 
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2014.0.4354 / Virus Database: 3722/7259 - Release Date:
> 03/27/14