Servidor DNS Raíz

DNS

Definición

Uno de los 13 clústeres de servidores raíz nombrados (A hasta M) que forman la cima de la jerarquía DNS. Los servidores raíz responden a consultas de la zona raíz dirigiendo a los resolvedores hacia los servidores de nombres TLD apropiados.

The Top of the DNS Hierarchy

Root servers are the authoritative DNSDomain Name System. The hierarchical, distributed naming system that translates human-readable domain names (e.g., example.com) into IP addresses (e.g., 93.184.216.34). Often called the "phonebook of the internet." servers for the DNS root zone — the zone that contains information about every TLDTop-Level Domain. The rightmost label in a domain name (e.g., .com, .org, .net). TLDs are managed by ICANN and include generic TLDs (gTLDs), country-code TLDs (ccTLDs like .kr, .uk), and sponsored TLDs (.edu, .gov). like .com, .org, .net, and all country-code TLDs. There are 13 root server addresses (labeled A through M), operated by 12 independent organizations including ICANN, Verisign, NASA, and several universities. Despite the appearance of only 13 servers, thousands of physical instances exist worldwide thanks to AnycastA network addressing method where the same IP address is assigned to multiple servers in different locations. Traffic is routed to the nearest or best-performing server, commonly used by CDNs and DNS providers. routing.

Anycast and the Actual Scale

Each of the 13 root server addresses is served by multiple physical servers in different geographic locations, all sharing the same anycast IP address. A resolver's query is automatically routed to the nearest instance. As of 2024, there are over 1,800 root server instances distributed globally, making the root server system one of the most resilient distributed systems ever built.

How Resolvers Use Root Servers

A recursive resolverA DNS resolution mode where the server performs the full lookup on behalf of the client, querying root, TLD, and authoritative servers in sequence until it finds the answer. Most DNS resolvers operate recursively. consults root servers only when it has no cached answer and no cached NS records for the target TLD. In practice, resolvers cache TLD NS records for 48 hours (the root zone's TTL (Time to Live)A field in an IP packet header that limits the packet's lifespan by specifying the maximum number of hops it can traverse. Each router decrements the TTL by one; when it reaches zero, the packet is discarded to prevent routing loops.), so the vast majority of resolution traffic never reaches root servers. Root servers receive roughly 500 billion queries per day globally, with most being garbage queries for non-existent TLDs and misconfigured devices. DNS Lookup

Términos relacionados

Más en DNS