What is domain name resolution?
Domain name resolution is the process of converting human-readable domain names (such as `www.example.com`) into IP addresses (such as `192.0.2.1`) that computers use for network communication. It is a fundamental component of the internet infrastructure, ensuring that users can access the correct server resources using simple web addresses. This process is carried out by the Domain Name System (DNS), which is distributed globally and functions as the “telephone book” of the internet.
The hierarchical structure of the Domain Name System (DNS)
DNS (Domain Name System) is organized using a hierarchical tree structure. At the top of this structure is the root domain name server, followed by the top-level domains (TLDs) such as `.com`, `.org`, `.cn`, and so on. Each top-level domain contains a large number of second-level domains (the domain names registered by users, such as `example`), and these second-level domains can further be divided into subdomains (such as `www`, `mail`). This hierarchical structure ensures the global uniqueness of domain names and enables efficient lookups.
The core participants in the parsing process
A complete domain name resolution process involves several key entities. The first entity is the DNS resolver, which is typically provided by the user's internet service provider (ISP) or a public DNS service (such as `8.8.8.8`). The DNS resolver receives query requests from the user's device and then seeks answers from the entire DNS system on behalf of the user. The next entity is the root domain name server, which directs the resolver to the appropriate top-level domain (TLD) server. The TLD server is responsible for managing the information of all subdomains under it and helps the resolver locate the authoritative name server for that domain. Finally, the authoritative name server, managed by the domain owner or hosting provider, stores the accurate information about the domain's records (such as A records and CNAME records).
The core principles and processes of domain name resolution
Domain name resolution is not a one-step process; rather, it is a sophisticated mechanism that combines recursive and iterative queries. When a user enters a website address in a browser, a series of invisible query interactions take place behind the scenes.
Recursive Queries and Iterative Queries
A recursive query refers to a request sent by a DNS client (such as a stub resolver on a user’s computer) to the local DNS resolver, with the request meaning “Please provide me with the final answer.” After accepting this request, the local DNS resolver initiates a series of iterative queries on behalf of the client within the DNS hierarchy. During an iterative query, if a server being asked does not know the answer, it does not attempt to find the answer itself; instead, it returns the address of a server that does know the answer for the next level of the query, allowing the client to proceed with the search. The local DNS resolver continues this process from the root servers, all the way to the TLD (Top-Level Domain) servers, until it finally finds an authoritative name server that can provide the desired IP address.
Recommended Reading What is a domain name and how does it work?。
Detailed explanation of the complete parsing steps
1. Local cache lookup: The user’s device first checks its DNS cache and Hosts file to see if there is an IP record for the domain name. If a record is found and it has not expired, the device uses that IP address directly, and the resolution process is completed.
2. Query the recursive resolver: If there is no local cache, the device will send the request to the configured local DNS resolver (recursive resolver).
3. The Iterative Query Process of the Parser: The local DNS resolver first checks its own cache. If no record is found, it begins an iterative query process:
* 询问根域名服务器：“`.com` 的TLD服务器地址是什么？”
* 根服务器返回 `.com` TLD服务器的地址。
* 询问 `.com` TLD服务器：“`example.com` 的权威名称服务器地址是什么？”
The TLD server returns the authoritative name server address for `example.com` (for example, `ns1.example-dns.com`).
4. Obtaining the final answer: The local DNS resolver queries the authoritative name server for `example.com`: “What is the IP address of www.example.com?”
5. Response and Caching: The authoritative name server returns the corresponding A record (IP address). The local DNS resolver then sends this result back to the user’s device and caches it for a certain period of time based on the TTL (Time To Live) value specified in the record, in order to handle similar queries in the future.
6. Establishing a connection: Once the user’s device obtains an IP address, it can establish a TCP connection with the target server and initiate an HTTP request.
Configuration and Management of Domain Name Records
The specific behavior of domain name resolution is achieved by configuring various DNS records. These records are stored on the authoritative name servers for the domain and serve as a set of instructions that guide the resolution process.
Common and Critical Types of DNS Records
- A Record (Address Record): The most fundamental record that directly maps a domain name to an IPv4 address. For example, it can map `@` (the root domain) or `www` to `192.0.2.1`.
- AAAA record: Similar to an A record, but it points to an IPv6 address.
- CNAME record (Canonical Name Record): This type of record maps a domain name to another domain name, rather than to an IP address. For example, if you set a CNAME record from `www.example.com` to `example.com`, any changes to the IP address of `example.com` will not require you to update the `www.example.com` record manually. However, it’s important to note that the target domain (in this case, `example.com`) cannot have any other types of records (such as MX records) associated with it. Additionally, resolving a CNAME record requires an extra lookup process during the domain name resolution.
- MX Record (Mail Exchange Record): Specifies the server address that receives emails for that domain name. The value includes the priority and the server domain name. For example, `10 mail.example.com`.
- TXT record: Used to store any text information, commonly used for domain name ownership verification (such as with Google Search Console), SPF (anti-spam), and DKIM (email signing) among other security configurations.
- NS record (Name Server record): Indicates which authoritative name server is responsible for resolving the domain name. This is the most critical record that needs to be set up with the domain name registrar.
- SOA Record (Start of Authority Record): Contains management information for the domain name, such as the primary name server, administrator's email address, serial number, refresh interval, and expiration time.
The Importance of TTL (Time To Live)
Each DNS record is accompanied by a TTL (Time To Live) value, measured in seconds. This value indicates how long DNS resolvers around the world can cache the record. A shorter TTL (for example, 300 seconds) means that changes to the record are quickly propagated globally, but it increases the load on the authoritative servers due to the frequent requests. A longer TTL (for example, 86,400 seconds, or 1 day) reduces the burden on the servers and speeds up subsequent queries, however, the propagation of record changes is much slower. When planning a server migration or an IP change, it is a standard best practice to lower the TTL in advance and then increase it again after the change is completed.
Domain Name Resolution Performance and Security Optimization
An efficient and secure DNS (Domain Name System) configuration can significantly improve website access speed, availability, and the ability to resist attacks.
Performance Optimization Strategies for Parsing
1. 选择优质的DNS服务商：使用提供全球任播网络、高可用性和低延迟的公共DNS解析服务（如Cloudflare DNS、Google Public DNS）或专业商业DNS服务（如AWS Route 53, Cloudflare, DNSPod），可以替代ISP可能较慢的默认解析器。
2. Set the TTL appropriately: Balance the flexibility of changes with the efficiency of caching by using a longer TTL for stable services.
3. 启用DNS预取/预连接：在网站HTML中通过 `<link rel=”dns-prefetch”>` 标签，提示浏览器对关键第三方域名（如CDN、字体、分析脚本）提前进行DNS解析，减少页面加载时的等待。
4. Reduce the number of CNAME redirection chains: Excessively long CNAME chains can increase the number of resolution attempts and prolong the resolution time. Try to direct the final record to an A/AAAA record.
Recommended Reading Domain Name Resolution and Configuration Guide: From Basic Concepts to Hands-On Operations。
Security reinforcement and protection
1. Deploying DNSSEC (Domain Name System Security Extensions): DNSSEC adds digital signatures to DNS data to prevent cache poisoning and DNS spoofing attacks, ensuring the authenticity and integrity of resolution results. An increasing number of registrars and DNS service providers support this feature.
2. Enable DNS over HTTPS (DoH) or DNS over TLS (DoT): These protocols encrypt DNS query requests and responses, preventing eavesdropping and man-in-the-middle attacks, thus protecting user privacy.
3. Protection against DDoS attacks: Choose a DNS service provider that offers the capability to handle large-scale distributed attacks, in order to defend against high-traffic distributed denial-of-service (DDoS) attacks targeting the domain name resolution layer and ensure that the resolution services remain uninterrupted.
4. Carefully manage API keys and permissions: Use a DNS management platform that supports detailed permission control to prevent domain name records from being maliciously altered due to the leakage of API keys.
summarize
Domain name resolution is the invisible foundation of internet access, and its principles, configuration, and optimization are essential knowledge that every website manager, developer, and operations personnel should master. From understanding the hierarchical structure and query process of DNS, to proficiently configuring various key records and setting appropriate TTL values, to actively implementing performance optimization and security enhancements, these steps form a complete cycle of domain name resolution management. A well-planned and maintained DNS setup not only improves the user experience and the reliability of websites but also serves as an important defense mechanism for building a secure network environment. As internet technology continues to evolve, staying up-to-date with new standards and practices such as DoH/DoT and DNSSEC will make your online services more robust and efficient.
FAQ Frequently Asked Questions
Why does it take time to take effect globally after modifying DNS records?
This is because recursive DNS resolvers around the world have cached the old records for your domain name. The time it takes for the changes to take effect depends on the TTL (Time To Live) value you previously set for that record. Until the TTL expires, the resolvers will continue to use the cached old IP address. Although you can update the record on the authoritative server immediately, the global cache needs to be refreshed as each TTL expires one by one. Therefore, it is standard practice to reduce the TTL value before making any important changes.
What's the difference between an A record and a CNAME record, and which one should I use?
The A record directly maps the hostname to a fixed IP address. The CNAME record, on the other hand, uses the hostname as an alias that points to another domain name (the canonical name); it is that domain name that ultimately determines the IP address.
If your server’s IP address remains stable, using an A record is the most direct and efficient method. If you are using third-party services such as CDN or cloud hosting platforms, their entry IP addresses may frequently change. In this case, it is best to set your subdomain (e.g., `www`) to point to the CNAME record provided by the service provider; the service provider will handle any IP address changes for you, eliminating the need for manual updates. However, it is generally not recommended to use CNAME records for the root domain (`@`, i.e., `example.com`) as this may cause conflicts with other necessary records (such as MX records).
What is DNS pollution/hijacking, and how to identify and deal with it?
DNS poisoning or hijacking refers to the malicious alteration of DNS resolution results, directing users to incorrect IP addresses (usually phishing websites or advertising pages). To determine if this is occurring, you can try using different public DNS services (such as `1.1.1.1` or `8.8.8.8`) to perform lookups and compare the results with the expected IP addresses. You can also use online DNS lookup tools to check the resolution from various locations around the world.
Recommended Reading In-Depth Analysis of the Domain Name System: A Complete Guide from Registration, Resolution to Security Management。
The measures to take include: configuring the use of trusted, encrypted public DNS services on terminal devices or routers (such as enabling DoH/DoT); checking whether local network devices have had their DNS settings altered by malware; for website owners, implementing DNSSEC can effectively prevent the resolution results from being tampered with during transmission.
What are the common reasons for domain name resolution failures?
Domain name resolution failures can be caused by various reasons: issues with the local network connection or incorrect DNS server configuration; the domain name registration has expired or was not renewed properly; the NS records (authoritative servers) for the domain name are set incorrectly, or the authoritative servers themselves are malfunctioning; there are errors in the DNS record configuration (for example, the IP address in the A record is incorrect, or necessary records are missing); firewalls or security software are blocking DNS query requests; or there are problems with the DNS service provider itself, such as a large-scale outage or a DDoS attack. When troubleshooting, it is advisable to follow a step-by-step approach, starting from checking local settings and gradually moving on to more complex issues.
What's next, what's next?
Extended reading and practical knowledge
The following are related to the topic of this article and are suitable for further in-depth reading. Prioritize starting with the article that is closest to your current problem, and gradually expanding to surrounding topics usually works better.
- Starting from scratch: A step-by-step guide on how to efficiently apply for and configure a personal website domain name
- What is a domain name? A comprehensive guide for beginners to experts, from registration to resolution.
- A detailed explanation of the entire domain name resolution process: from entering a website address to the behind-the-scenes journey of loading the web page
- What is a domain name? A comprehensive explanation of its definition, types, and common questions.
- Domain Name Resolution and DNS Configuration: A Comprehensive Guide from Beginner to Expert
English