There Are Only 13 Named DNS Root Servers. There Are Also About 2,048 Machines Answering to Them.

Every time a device looks up a domain name for the first time, the query eventually has to start somewhere. That somewhere is the DNS root, and it is defined as exactly 13 named server identities, lettered A through M. Almost nobody who quotes that number knows why it stopped at 13, or that it has almost nothing to do with the number of actual machines.

Why 13, specifically

• The DNS specification, RFC 1035, was published in 1987. At the time, DNS responses traveled over UDP, which had a practical unfragmented packet limit of 512 bytes.
• A resolver's very first query needs a reply listing every root server's name and address, so the whole client can even start working. That reply has to fit inside one UDP packet, or resolution gets a lot more complicated.
• Working backward from DNS wire format, 13 name and IPv4 address pairs was the maximum that fit inside that 512 byte ceiling. Not 12, not 14. Thirteen was the hard limit.
• When IPv6 addresses were added decades later, the responses grew past 512 bytes, but by then an extension called EDNS0 existed to carry larger replies. The number 13 was already frozen into every resolver on earth, so it stayed.

How 13 names turned into thousands of machines

• Each of the 13 named identities is not one computer. It is an anycast address: the same IP address is announced from many physical locations around the world simultaneously, and network routing sends each query to whichever instance is topologically closest.
• Per the official root server operators' own live tracking site, the system currently runs about 2,048 operational physical instances answering for those 13 names, spread across every populated continent.
• This is why a root server outage almost never makes the news anymore. Taking down any single physical machine just means traffic quietly reroutes to the next nearest instance answering the same address.

The part that is easy to miss
No single organization runs all 13. Operational responsibility is deliberately spread across a mix of government agencies, universities, and non-profit infrastructure bodies on different continents, specifically so that no one outage, company decision, or jurisdiction can take the whole system down at once. The number 13 is a frozen protocol artifact. The redundancy behind it is a deliberate governance choice.

Sources: IANA's official root server list (iana.org/domains/root/servers) and the root server operators' live instance count (root-servers.org), RFC 1035 (1987).