You type a website name into your browser, press Enter, and expect a page to appear. But your device needs an internet address, not just a memorable name, to find the destination. DNS helps connect those two pieces.
Understanding what DNS is also explains a familiar frustration: a website may be running normally, yet your browser says it cannot find it. Sometimes the problem is not the website. It is the process of locating its address.
DNS meaning: the internet’s naming system
DNS stands for Domain Name System. This distributed naming service lets computers look up information associated with domain names, including IP addresses. Instead of remembering a numerical address, you enter a name such as example.com. A DNS lookup can return the information needed to reach that site.
DNS does not deliver the webpage or establish the browser’s encrypted connection. It helps identify where a connection should go. Other internet protocols handle the connection and data transfer. For more background, see our guide to IP addresses and how devices communicate.
How a DNS lookup finds the right address
A lookup often happens so quickly that you never notice it. The exact sequence depends on your device, its caches, and the resolver configured for your network.
First, your device checks what it knows
Your browser or operating system may have an answer from an earlier visit. If that cached answer is still usable, it may not need to contact another DNS server. This saves time and reduces unnecessary requests.
Next, a recursive resolver searches
Otherwise, your device typically asks a recursive DNS resolver, often supplied by your internet service provider. A workplace network or public DNS service can provide one instead. The resolver either answers from its own cache or obtains the information from other DNS servers.
Then, the DNS hierarchy supplies directions
For an uncached lookup, the resolver may consult root servers, which direct it toward servers responsible for a top-level domain such as .com. Those servers identify the domain’s authoritative name servers. An authoritative server supplies the DNS records for the domain.
The resolver returns the result to your device, which can then attempt to connect. Think of this as following a series of directories rather than opening one giant global address book.
What information do DNS records contain?
DNS has several record types, each with a specific job. An A record associates a name with an IPv4 address, while an AAAA record provides an IPv6 address. A CNAME record makes one name an alias of another name.
Other records serve different purposes. MX records identify mail servers, TXT records can carry domain-verification or email-authentication data, and NS records identify authoritative name servers for a zone. A site may also have multiple IP addresses, so not every visitor necessarily receives the same answer.
These records provide directions, not a guarantee that the website’s server will respond. A perfectly valid address can still lead to a timeout if the server or network is unavailable.
Why DNS updates take time
Imagine moving a website to a new hosting provider. You change its A record, but your laptop still reaches the old server while a colleague sees the new one. That does not necessarily mean the change failed.
DNS answers are commonly cached. A record’s time to live, or TTL, guides how long resolvers can retain an answer before refreshing it. Different caches may still hold different answers. Browsers and operating systems can have their own caches, too.
During a website migration, record the old and new addresses so you can compare lookup results with the expected destination. Our guide to website hosting and domain settings provides useful context for these changes.
Why DNS problems stop sites from loading
Several problems can prevent a name from resolving: a typing mistake, missing records, an unreachable resolver, incorrect name-server settings, or a misconfigured domain. A browser’s address-related error does not by itself identify which one is responsible.
Diagnostic tools may show NXDOMAIN when a requested name does not exist. SERVFAIL means the resolver could not complete the request; unreachable authoritative servers or DNSSEC validation problems are among the possible causes. Neither response automatically means the website’s files are gone.
And if DNS returns an address but the page still times out, the fault may lie elsewhere, including the network route, firewall, or web server. Successful name resolution is only the beginning of a working visit.
How to test a possible DNS problem
First, try several unrelated websites. Next, test the problem site on another connection, such as mobile data instead of home Wi-Fi. If it works on one network but not the other, a network-specific resolver or cached answer deserves investigation.
On Windows, open Command Prompt and enter nslookup example.com, replacing the example with the affected domain. On macOS or Linux, you can use dig example.com if that tool is installed. Check whether the returned address matches what the website’s hosting provider expects.
If the issue affects only your device, restarting the browser or clearing its DNS cache may help. If many domains fail, investigate your connection, router, and configured DNS resolver. Temporarily testing a reputable public resolver can help isolate a resolver problem, but it cannot fix missing authoritative records.
Make one change at a time. Our overview of common internet connection problems can help you distinguish DNS failures from wider network trouble.
Is DNS private and secure?
Traditional DNS queries often travel without encryption, so parties with network visibility may be able to observe requested names. DNS over HTTPS and DNS over TLS can encrypt queries between your device and a compatible resolver. Neither feature makes your browsing anonymous.
DNSSEC serves another purpose: it helps validating resolvers check that signed DNS information is authentic. It does not encrypt DNS queries or replace HTTPS for protecting website traffic. DNS privacy, DNS integrity, and connection security solve different problems.
Frequently asked questions
Is DNS the same as an IP address?
No. An IP address identifies a network destination. DNS is the naming system that helps associate domain names with addresses and other information.
What is a DNS server?
It is a server that answers DNS questions. Recursive resolvers find answers for users, while authoritative servers provide records for the domains they serve.
Can a website work while DNS is down?
Sometimes. Existing connections or cached answers may keep working. New connections that need an unavailable lookup can fail even when the web server is healthy.
Will changing DNS make my internet faster?
A faster resolver may shorten some name lookups, but it does not automatically increase your broadband speed or accelerate large downloads.
What to remember about DNS
DNS connects names people remember to information computers use to find destinations. Its servers, records, and caches make everyday browsing possible. When a site refuses to load, checking whether the name resolves is a practical first step toward finding the real problem.
