4 ms·
Out of curiosity, how big (in GBs/TBs) are the root files? If I setup a local DNS server (Raspberry or something more powerful) could I duplicate or cache the r
by NKosmatos 6y ago
Out of curiosity, how big (in GBs/TBs) are the root files? If I setup a local DNS server (Raspberry or something more powerful) could I duplicate or cache the root file somehow?
IMHO the various ISPs should contribute to the cost and technical needs of the root servers or even better utilize blockchain, torrent or other distributed network concepts.
- vesinisa 6y agoThe root zone has grown considerably thanks to a number of new gTLDs, but currently sits at around 2 MB: https://www.iana.org/domains/root/files https://www.iana.org/domains/root/files That's in human-readable ASCII. A wire format could probably shave a chunck off that, but distributing deltas instead of re-downloading the whole file each time a change is made would further reduce the required data transfer amounts to mere bytes per day on average.
- NKosmatos 6y agoThanks for your reply, I was thinking about the actual files containing the DNS entries and not the root file which contains all of the DNS servers. As I understand it the root file is needed in case you want to bootstrap your own DNS server so as to be able to find all the other authoritative servers. What about the actual DNS database files?
- vesinisa 6y agoYou are talking about the root seed list (the NS records for the root label .) - essentially the anycast IPv4/6 addresses for the 13 root servers. This file is provided in the first section of the linked page. The second file on the page contains the actual current root zone, which is a 2 MB file containing all the delegation entries for TLDs (like com., org. and de.) immediately below the DNS root (.). This is what the article is talking about caching locally at your ISP's recursive name server. The whole global DNS can never be downloaded or even built as a local database due to its distributed nature, and also for technical reasons. Below the root zone at TLD level (like com.) there is no way to enumerate all the individual registrations (like google.com., ycombinator.com., microsoft.com. etc) You always query for a specific individual name + record pair, instead of being allowed to download the entire zone. So even if you somehow would be able to contact every authoritative DNS server on Internet at some point in time, there is no standard query to ask them to give you all their records, making building a full local copy of the global DNS database impossible.
- 1vuio0pswjnm7 6y agoftp -4o/dev/fd/1 ftp://192.0.32.9/domain/root.zone|dd >/dev/null 2165210 bytes (2.2 MB, 2.1 MiB) Anyone can serve their own root.zone. I have done so for many years. The web might be "big" but the portion of it you as a personal user are accessing is comparatively small. If you tally up all the domains you are currently visiting (excluding nonsense like ad servers), chances are, a zone file that contains the RRs for every domain you will ever need to visit in your entire lifetime would fit on a small-sized USB stick from 10 years ago. You can effectively avoid recursion. 100% authoritative DNS, all served from your computer. Today's USB sticks can accomodate the largest zones like .com several times over. That is more web than you could possibly surf in your lifetime.