[Bender]

Just to have a compressed static file that contains all the routes one could download from time to time I think would be interesting to analyze. Same goes for the anycast root DNS servers. To have a full dump from them could be interesting. Not to be confused with the root.zone [1] I mean the whole kit and caboodle.

[1] - https://www.internic.net/domain/root.zone

[icehawk]

RIPE keeps this https://ris.ripe.net/docs/mrt/#name-and-location

[Bender]

The collectors are browsable nice, Thankyou!

The collectors seem to be overloaded so made a temporary mirror of the one for AMS In AMS. [1] I only mirrored the latest files. Feel free to beat it up. The .gz files decompress to just under 4GB

[1] - https://ams.nochan.net/data.ris.ripe.net/rrc00/

[Bender]

No interest in this mirror, gonna nuke it.

[johnhtodd]

This is conflating BGP routes and DNS.

DNS data: Root server data is available via AXFR ("dig . AXFR @f.root-servers.net") but this isn't what you're referencing.

Second level TLD server data is available is available at CZDS. (https://czds.icann.org/home) but some TLDs don't participate, but this also isn't what you're referencing.

What I think you want: There is no canonical list of all zones that exist - there is no "central repository" once you pass the root zone downwards - that's a feature, not a bug. Some organizations have partial views based on large recursive resolver data (DomainTools, Google, Cisco, Cloudflare, Quad9) but access to that data is limited to vetted researchers or more typically only available at a cost (disclaimer: I work for Quad9.) Smaller versions of recursive data sets exist, but are usually significantly limited by geography and demographics of the user community that generates the data set.

BGP route data: This exists in many forms in realtime like the site referenced above, though historic data is difficult to track. No matter what the source or latency, there is bias in the data set because BGP pathing is unique to each ASN that collects it - no two views of the table are identical, and any data set is as "best guess" at state conditions at that time.

Here are some possible data sets for BGP:

Packet Clearing House (PCH) provides a set of snapshots going back 20+ years (though it seems to be offline at the moment): https://www.pch.net/resources/Routing_Data/

Cymru has a live version you can query via various APIs (including ironically via DNS): https://www.team-cymru.com/ip-asn-mapping

Routeviews from University of Oregon also has a data set that is widely used by researchers: https://www.routeviews.org/routeviews/

[Bender]

This is conflating BGP routes and DNS.

No I was fantasizing that I could get these two things. They are two separate things. If I had a nickle for every time I said something off topic I could by everyone a cup of coffee.

[toast0]

> Just to have a compressed static file that contains all the routes one could download from time to time I think would be interesting to analyze.

When I needed this for some work stuff, it was pretty easy to find table dumps and work with them? I don't remember where it was, but I'm sure you can find some. After an acquisition, we had our own ASN and I was able to get table dumps from our own infrastructure.

> Same goes for the anycast root DNS servers. To have a full dump from them could be interesting. Not to be confused with the root.zone [1] I mean the whole kit and caboodle.

What do you think the root servers have that's not in the root.zone? I think you can AXFR from the root servers, too, but it should be the same thing as from the https site.

[Bender]

What do you think the root servers have that's not in the root.zone?

Every glue record for every domain name. The glue is the valuable goo. Without the goo everyone goes back to /etc/hosts which I am not opposed to.

[toast0]

The root servers don't have the glue record for every domain name though. All they have is the glue records for the TLDs. (which is in the zone file you linked)

[Bender]

Every time I stand up new name servers I have to add the glue records into the root servers or the name servers do not exist. In fairness to me I keep forgetting the trend is to shove everything into big centralized DNS servers as it is something I would never do at least not as a primary.

[toast0]

Afaik, those glue records are held at your TLD's registry and served by the tld nameservers, not the root servers.

It might be nice to get a zone transfer for every tld, but that's not possible for the public. (I understand there's some way to get many of them, but $$$$)

[Bender]

I run my own name servers. I never use the name servers of a registry. I can see the glue records of my name servers in the root servers. In fact the reason I left NetworkSolutions (web.com) was that their interface to update the root servers broke and there was nobody left that knew how to fix it. I'm sure they must have fixed it by now but I was being impatient only waiting 3 weeks.

I should add that I have been adding name servers to the root servers since 1998. I've just never managed one of the root servers and I guess nobody on HN has either.