The Domain Name System (DNS) translates domain names into IP addresses. Learn how DNS works, the main record types and why DNS matters for SEO and site migrations.

Summary
The Domain Name System (DNS) is the internet's directory: it translates a domain name such as sorank.com into the IP address of the server that hosts the site.
Want to go further? Ask
The Domain Name System (DNS) is the system that translates human-readable domain names, such as example.com, into the numeric IP addresses that computers use to locate servers. Every time someone opens a web page, sends an email or a search engine bot fetches a URL, a DNS lookup happens first, usually in a few milliseconds.
DNS is often described as the phone book of the internet. It is invisible when it works and blocking when it fails: if DNS is down or misconfigured, the site is unreachable for visitors and for crawlers alike, regardless of the quality of its content.
DNS is a distributed, hierarchical database created in 1983 and standardized in RFC 1034 and RFC 1035 (1987). No single server holds every record. Instead, responsibility is split between root servers, top-level domain servers (.com, .fr, .de) and the authoritative name servers chosen by each domain owner, usually at a registrar, a host or a provider such as Cloudflare.
A domain name is the readable part of a URL. DNS links that name to technical resources: the web server, the mail servers, verification tokens for third-party services. Changing these links is done by editing DNS records in the zone of the domain.
When a browser needs the IP address of www.example.com, it first asks a recursive resolver, typically run by the internet provider or a public service such as 1.1.1.1 or 8.8.8.8. If the answer is not cached, the resolver asks a root server, which points to the .com servers, which point to the authoritative name servers of example.com, which finally return the IP address.
Each answer comes with a TTL (time to live) that tells resolvers how long to cache it. A long TTL reduces lookups and speeds up repeat visits; a short TTL lets changes propagate faster. This is why DNS changes can take from a few minutes to 48 hours to be visible everywhere.
A DNS zone contains several kinds of records, each with a precise role:
Less common records include CAA (which certificate authorities may issue SSL certificates), SRV (services) and PTR (reverse lookups). For a marketing site, A, AAAA, CNAME, MX and TXT cover almost every need.
DNS is not a ranking factor in itself, but it influences two things that matter. The first is availability: if name servers fail, Googlebot cannot reach the site, and repeated failures reduce crawling. The second is speed: DNS resolution is the first step of every page load, and slow resolution adds latency before the first byte, which weighs on page speed for first-time visitors.
Most modern DNS providers answer in a few milliseconds from many locations. Fast, anycast DNS, often bundled with a content delivery network, removes this bottleneck. Choosing a reliable provider with redundancy is a simple way to protect both users and crawlers.
DNS is involved in several everyday SEO tasks. Verifying a domain property in Google Search Console uses a TXT record, which covers every protocol and subdomain at once. Pointing a blog subdomain to a hosted platform uses a CNAME. Email deliverability for newsletters relies on SPF, DKIM and DMARC records.
Migrations are the riskiest moment. Moving a site to a new host or a new domain means changing records, and a mistake can take the whole site offline or break HTTPS. Lower the TTL a day before, change records during a quiet period, check that every old URL returns the right status with a redirect checker, and monitor crawl errors in the following days.
The most frequent mistakes are letting the domain expire, deleting a record still used by a service, and leaving two conflicting records for the same name. Another classic error is pointing the root domain and the www version to different servers, which creates duplicate versions of the site if redirects are not set.
Security is the other risk. Dangling CNAME records pointing to deleted cloud resources can be taken over by attackers, and unlocked domains can be hijacked. Enable registrar lock, two-factor authentication on the registrar account, and DNSSEC where supported.
For SEO, DNS is part of the invisible foundation: a site that resolves quickly and reliably is crawled consistently and loads faster for real users. Problems at this level cancel out all content and link work, because pages that cannot be reached cannot be indexed.
For GEO, the same rule applies to AI crawlers such as GPTBot, ClaudeBot or PerplexityBot. They fetch pages over the same DNS and HTTP stack as Googlebot. When an AI assistant tries to read a page in real time to answer a question and the domain does not resolve, the page is simply skipped in favor of another source.
The Domain Name System translates domain names into IP addresses through a hierarchy of resolvers and name servers, with records such as A, CNAME, MX and TXT. It is not a ranking factor, but it conditions availability, speed, site verification and migrations, which makes it a quiet prerequisite of SEO and GEO.
Reference sources: MDN Web Docs and Wikipedia.
Sources
DNS stands for Domain Name System. It translates domain names such as example.com into the IP addresses of the servers that host websites, email and other services.
It depends on the TTL of the record and on resolver caches. Many changes are visible within minutes, but it can take up to 48 hours everywhere. Lowering the TTL before a planned change speeds up propagation.
Indirectly, yes. If the domain does not resolve, Googlebot cannot crawl the site and users cannot reach it. Short outages are usually harmless, but repeated or long failures reduce crawling and can lead to pages dropping from the index.
THEY TRIED SORANK BEFORE YOU
