Fundamentals 9 min read

Understanding DNS: Structure, Types, and Resolution Process

This article explains the fundamentals of the Domain Name System (DNS), covering its hierarchical structure, the different types of top‑level domains, and the detailed nine‑step process by which a user's request is resolved from a human‑readable URL to an IP address.

Architecture Digest
Architecture Digest
Architecture Digest
Understanding DNS: Structure, Types, and Resolution Process

During a recent interview the candidate was asked about the DNS request process, prompting a review of the definitions and principles involved in DNS resolution.

DNS (Domain Name System) is a distributed database that maps human‑readable domain names (e.g., www.51cto.com) to IP addresses, allowing users to access internet resources without memorizing numeric addresses. The hierarchy consists of three layers: the Root DNS servers, the top‑level domain (TLD) servers (including gTLD, ccTLD, and New gTLD), and the local DNS servers operated by ISPs or organizations.

Top‑level domains are categorized into:

gTLD (generic top‑level domains) such as .com, .net, .org.

ccTLD (country‑code top‑level domains) such as .cn, .jp.

New gTLD (new generic domains) such as .xyz, .top, .red, .help.

Below the TLD servers are local DNS servers that cache recent query results and serve nearby users.

DNS resolution follows a nine‑step workflow:

The browser checks its cache for the URL‑IP mapping.

The local hosts file is consulted for any static mappings.

The request is sent to the local DNS server, which may already have the answer.

If not, the local server queries a Root DNS server to obtain the address of the appropriate TLD server.

The TLD server returns the authoritative Name Server address for the domain.

The Name Server provides the domain’s A (address) or CNAME (alias) record and a TTL (time‑to‑live) value.

If an A record is returned, the client can directly contact the target IP; otherwise, a CNAME may redirect to a Global Traffic Manager (GTM) for load balancing.

The GTM directs the request to the nearest CDN cache server, which serves static assets (HTML, CSS, JS, images).

Dynamic content (e.g., product or order data) is fetched from the application server behind a load balancer.

GTM (Global Traffic Manager) and CDN (Content Delivery Network) work together to route users to the most optimal server based on proximity, performance, and health, ensuring high availability and fast response times.

In summary, DNS translates domain names to IP addresses through a three‑tier hierarchy—Root, TLD, and Local DNS—while additional services like GTM and CDN enhance performance and reliability for both static and dynamic web resources.

CDNnetworkingDNSDomain Name SysteminternetGTM
Architecture Digest
Written by

Architecture Digest

Focusing on Java backend development, covering application architecture from top-tier internet companies (high availability, high performance, high stability), big data, machine learning, Java architecture, and other popular fields.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.