Device → Recursive resolver → Root → Top-level domain → Authoritative server → Answer returned to device
| Record | Typical use | Important distinction |
|---|---|---|
| A / AAAA | IPv4 / IPv6 address | Not proof the website works |
| CNAME | Alias to another DNS name | Not an HTTP redirect |
| MX | Mail exchanger | Not the web host |
| TXT | Verification and policy text | Not a browser instruction |
What DNS Actually Does
The Domain Name System, or DNS, is the distributed naming infrastructure that helps software discover information associated with domain names. People remember a name more easily than a numerical internet address. A browser can ask a DNS resolver for address records associated with a hostname, then use the answer to attempt a network connection. DNS is not the entire internet and does not guarantee that a website is available. It is a database with a delegation hierarchy, caches, record types, and organizations responsible for different parts of a name. It also supports email routing and service verification.
A domain is a human-readable identifier in a naming hierarchy. A hostname identifies a network endpoint or service. An IP address is a network-layer address. A website is an application that receives requests and sends content. These concepts are related, but not interchangeable. If a website changes hosting providers, its DNS answers may change while the domain stays the same. A domain may resolve successfully even if the server is down or the HTTPS certificate is invalid.
Answers can vary by time, network, geographic location, and requested record type. Large services often distribute traffic across several addresses or locations. Some hostnames offer both IPv4 and IPv6 addresses. A lookup supplies information needed to attempt a connection, not proof that the destination is reachable.
How A DNS Lookup Works
When you enter a web address, the browser interprets the URL. The scheme, such as https, indicates the protocol, the hostname identifies a name that may need resolving, and the path specifies the requested resource. The browser or operating system might already have a cached answer. Otherwise, the device typically asks a configured recursive resolver. That resolver may be provided by a router, internet provider, employer, or separately selected service. Some browsers use encrypted DNS independently of the operating system.
If the recursive resolver lacks a cached answer, it can follow the DNS delegation hierarchy. Root name servers refer it toward the relevant top-level domain servers, which in turn indicate the authoritative name servers for the domain. An authoritative server provides records or an appropriate negative answer. The recursive resolver returns the result to the client and may cache it for the allowed time. Most ordinary lookups do not require contacting root servers because caching avoids repeated work.
The browser can then attempt to establish a connection, negotiate TLS for HTTPS, and request content using HTTP. The exact sequence depends on protocol and browser behavior, but resolution and connection are different stages. An address lookup can succeed while the server fails, the certificate is rejected, or the requested page returns an error. Troubleshooting improves when each stage is tested separately.
Resolvers, Authoritative Servers, And Registrars
A recursive resolver works on behalf of clients. It receives a question, obtains or reuses the relevant DNS data, and returns an answer or error. A home router often forwards queries to an upstream resolver rather than following the entire hierarchy itself. An authoritative server publishes records for a zone that an organization manages. It is not ordinarily responsible for performing arbitrary recursive searches on behalf of every internet user.
A registrar is the business through which a domain name is registered. A registry operates a top-level domain and maintains delegation information. A hosting provider runs the website or application. A DNS hosting provider runs authoritative name servers. One company can offer all these services, but their technical roles remain distinct. Knowing which company controls which layer matters when changing a domain.
Imagine registering a domain with one company, hosting the website with another, and operating DNS through a third. The registrar controls the delegation to authoritative name servers. The DNS host controls the records published inside the zone. The web host controls whether the application responds. Changing a DNS record in an inactive provider dashboard will not affect the public answer. Replacing an entire zone during a website migration can also interrupt mail or domain verification. Identify the actual authoritative provider before editing production records.
Important DNS Record Types
An A record associates a name with an IPv4 address. An AAAA record provides an IPv6 address. A hostname may publish several addresses of either type, and different clients may select different ones. A CNAME record aliases one DNS name to another. A CNAME is not the same as an HTTP redirect: the browser does not automatically change the URL merely because the name is an alias. DNS rules constrain which other records can coexist at the same CNAME owner name.
MX records identify mail exchangers and include preference values. TXT records hold text used for many purposes, including domain verification and email authentication. NS records identify name servers for zones or delegations. SOA records contain administrative parameters for a DNS zone. PTR records support reverse DNS mapping. CAA records can restrict which certificate authorities are authorized to issue certificates for a domain. SRV, HTTPS, and SVCB records serve specialized discovery or service-binding purposes.
Do not assume that an A lookup reveals the complete configuration of a domain. A website might depend on IPv6, a mail service might depend on MX and TXT records, and a service might publish specialized records. Before making changes, inventory the records needed by every application using the domain. The exact meaning of a record depends on its type, owner name, and surrounding configuration.
Caching, TTL, And DNS Changes
Caching is essential to DNS performance. A resolver can reuse a recent answer instead of contacting authoritative infrastructure on every request. Record sets normally have a time to live, or TTL, indicating how long cached data can be reused under normal rules. A TTL of 300 seconds means five minutes, but it does not guarantee that every device worldwide will show a changed record exactly five minutes after an administrator presses Save. Different caches may have obtained the old value at different times.
The phrase DNS propagation is convenient but potentially misleading. Authoritative servers publish new information; old cached answers gradually expire. There is not one global broadcast that updates all devices simultaneously. Browsers, operating systems, recursive resolvers, and applications may cache results differently. Negative answers can also be cached. Delegation changes can involve additional layers of cached information.
For a planned migration, reduce relevant TTL values sufficiently in advance, prepare the new destination, and preserve the old service during the transition where practical. Reducing a TTL at the moment of a change does not shorten an older answer that has already been cached with a longer lifetime. Compare authoritative answers with the resolver actually used by an affected client. Repeatedly flushing every device is not a substitute for checking whether the correct records were published.
IPv4, IPv6, And Different Answers
IPv4 addresses use four decimal groups separated by dots. IPv6 addresses use hexadecimal groups separated by colons. Documentation addresses such as 192.0.2.10 and 2001:db8::10 are reserved for examples, not real public production endpoints. A hostname may have an A record, an AAAA record, both, or neither depending on its purpose. Modern devices can choose among available addresses using connection-selection behavior more sophisticated than always picking one fixed answer.
If IPv6 connectivity is broken on a network, symptoms may seem intermittent when some applications or connection attempts use IPv6 and others use IPv4. However, disabling IPv6 everywhere is not a sound first step. It may mask the problem, break features, or conflict with managed network policy. Compare record answers, inspect actual IPv4 and IPv6 connectivity, and use tools that explicitly test each family when available.
Multiple answers are not automatically signs of an error. Large websites use load balancing, proxies, and content-delivery networks. A public lookup service in one country may show a different address from the one returned to your home network. Both can be valid. Focus on whether the answer belongs to the intended service and whether the subsequent connection works. Do not assume that every resolver should return the same address at the same moment.
DNS Versus URLs, Hosting, And HTTP
A URL identifies a resource and can contain a scheme, hostname, port, path, query, and fragment. DNS generally resolves the hostname rather than interpreting the entire URL. A search engine indexes and ranks content, while DNS provides naming information. Typing a question into a browser address bar can invoke search, but that is a browser feature rather than a DNS operation. A domain can resolve correctly while its pages are absent from search results.
Web hosting runs the application and serves files. DNS does not normally store the site’s articles, images, or database. HTTP governs application requests and responses, while HTTPS uses TLS to protect transport and authenticate the service. A 404 page can occur after successful DNS resolution because the requested resource is missing. A server error or certificate warning can likewise occur after the browser has already found the destination.
Cloud platforms often place registration, DNS, hosting, storage, and certificates inside one dashboard. That convenience does not make them one technical function. Our cloud computing guide explains the infrastructure behind remote applications, and the technology glossary defines terminology used in network settings. When diagnosing a failure, identify the stage rather than treating every website problem as a DNS problem.
Check DNS On Windows, macOS, And Linux
Begin by observing whether the failure affects one website, one device, or the whole network. Check whether another trusted site loads and whether a second device on the same connection behaves differently. Avoid immediately changing resolver settings or installing a third-party network repair tool. The pattern of failure is often more informative than a random series of commands. Read our command-line beginner guide if terminal syntax is unfamiliar.
On Windows, open Command Prompt or PowerShell and run nslookup example.com. It displays the resolver and answer, although formatting varies. Supported versions of PowerShell also provide Resolve-DnsName example.com. On macOS and many Linux systems, dig example.com is a common utility when installed. These commands generally perform read-only queries. Do not paste unfamiliar administrative scripts from websites into a terminal.
To inspect a specific type, try nslookup -type=MX example.com or dig example.com MX. To compare a selected resolver, nslookup example.com 1.1.1.1 or dig @1.1.1.1 example.com queries that resolver if the network permits it. A browser configured for secure DNS may use a different resolver from the operating system. Record the name, record type, resolver, result, and timestamp. Do not send private workplace hostnames to external public resolvers without authorization.
Interpret DNS Errors Correctly
A successful answer with address records indicates that a resolver found relevant data. It does not establish that the website is online. NXDOMAIN means the queried DNS name does not exist in the answer returned by that resolver. Possible causes include a typo, a missing name, or incorrect configuration. NOERROR without the requested record can mean that the name exists but has no record of that type. SERVFAIL means the resolver could not successfully complete the request, potentially because of upstream failures or DNSSEC validation issues.
A timeout means that no answer arrived within the tool’s waiting period. It is not definitive proof that a name does not exist. A non-authoritative answer usually means a recursive resolver supplied the data rather than an authoritative server. That is normal for ordinary client lookups. Different answers across resolvers can reflect caching, geographic routing, filtering, or inconsistent records. Compare the exact query, type, time, and source before drawing conclusions.
A browser’s DNS error is a starting clue rather than a complete diagnosis. A failed ping is not proof of DNS failure because a server can reject ICMP traffic while serving HTTPS normally. Separate the lookup, connection, TLS, and HTTP response. A methodical diagnosis saves time and avoids changing settings that cannot plausibly affect the failing stage.
Troubleshoot DNS Problems Safely
Start with the hostname spelling and whether the intended website works on another device or connection. If only one app fails, inspect that app’s proxy, VPN, or encrypted DNS settings. If every device on the router has trouble resolving names, examine router status and provider outage notices. If one device fails while others work, inspect its assigned resolver, VPN configuration, and recent software changes. Avoid resetting the router or the entire computer before collecting evidence.
Restarting a browser or reconnecting to a network is usually less disruptive than resetting all network settings. A cache flush may help when a device retains an obsolete answer, but it is not a universal fix. On Windows, ipconfig /flushdns clears the Windows DNS resolver cache. It does not update authoritative records, repair a failed server, or guarantee that every browser cache is cleared. On managed systems, consult the administrator before altering settings.
Switching to a public resolver can isolate a resolver-specific problem, but it changes privacy and policy relationships. Write down the original settings before making a reversible change. Public resolvers may not know private workplace names. Changing DNS can bypass intended family filtering or security controls. A VPN may require specific internal resolvers. The safest fix is one supported by a clear observation, not whichever online checklist contains the most commands.
Encrypted DNS, DNSSEC, And Privacy
Traditional DNS queries have often traveled without application-layer encryption, allowing some network observers to see requested names. DNS over HTTPS and DNS over TLS encrypt traffic between a client and its chosen resolver. They can protect queries on that segment but do not make browsing anonymous. The resolver can still process the names, and websites, network metadata, browser accounts, and other systems may reveal activity. Privacy depends on the complete connection and the resolver’s policies.
DNSSEC is a separate mechanism. It provides signatures that validating resolvers can use to check the authenticity and integrity of signed DNS data within a chain of trust. It does not encrypt DNS questions or guarantee that a website is trustworthy. A misconfigured DNSSEC deployment can cause validating resolvers to return SERVFAIL even when a nonvalidating tool appears to find an address. Administrators should carefully plan DNSSEC changes when moving DNS providers.
Security products may filter DNS responses to block malicious domains, but filtering can produce false positives. DNS is only one layer of protection. Browser updates, operating-system patches, HTTPS certificate validation, secure account practices, and cautious downloads remain necessary. Our Windows Update troubleshooting guide covers how to recover safely when important system updates fail.
DNS Changes For Website Owners
Before editing production DNS, inventory all services using the domain. Websites, email, verification tokens, subdomains, and integrations may rely on different records. Export the current zone if the provider allows it, or record existing values and timestamps. Confirm which authoritative servers are delegated at the registrar. Editing an inactive DNS dashboard may appear successful without changing the public answers.
For a website move, prepare the destination first. Verify that it can serve the correct hostname, that HTTPS certificates can be issued, and that redirects and application settings are ready. Then change only the required records and monitor authoritative and recursive answers. Do not remove MX or TXT records just because a hosting wizard proposes replacing an entire zone. If the move also changes DNS providers, copy all necessary records before changing delegation.
Email requires special care. MX records, SPF, DKIM, DMARC, and service-specific verification entries may need coordinated updates. Incorrect records can delay mail or cause authentication failures while the website continues working. Maintain registrar account security, recovery access, and renewal reminders. Keep a rollback plan and understand that cached answers can delay the effect of reversing a change. DNS is infrastructure: treat changes as controlled operations rather than experiments on a live business domain.
DNS Myths That Cause Bad Fixes
Changing DNS does not automatically make internet access faster. A responsive resolver can reduce some lookup delays, but it cannot increase broadband bandwidth or repair weak wireless signals. Browsers cache answers and reuse connections, so lookup time may be a small part of the total experience. Performance varies by region, network, and the sites being tested. Measure relevant tasks before and after a reversible change instead of trusting one promotional benchmark.
Flushing DNS does not repair every connectivity failure. It removes certain cached answers, not defective Wi-Fi hardware, a failed internet provider, a broken cable, or an offline web server. If the wireless connection itself disappears, consult our Wi-Fi troubleshooting guide. If the computer is generally slow, our slow Windows 11 PC guide explains performance symptoms that may resemble network delays.
A DNS record also does not necessarily identify one physical machine. Load balancers, shared hosting, reverse proxies, and content-delivery networks make that assumption unreliable. A technically valid DNS response is not proof that a website or email sender is legitimate. Attackers can register domains and configure functional DNS and HTTPS. Treat a lookup as infrastructure evidence, not a trust verdict.
A Safe DNS Learning Exercise
You can learn DNS without changing router settings or owning a domain. Start with the public documentation name example.com. Predict what an A lookup will return, then run it and record the result. Repeat with AAAA. Notice that record types can provide different information. A missing AAAA record does not automatically mean a site is broken; the service may not publish IPv6 for that hostname.
Next, query MX records and compare them with address records. You are observing different services represented by the same naming infrastructure. Compare the same query against two resolvers if your network permits it, noting the TTL and any differences. Use only public demonstration names, not private company hostnames. If the answers differ, consider caching and service distribution before assuming either answer is malicious.
Practice diagnosing a DNS incident: one browser cannot open a site, but a phone on the same network can. List the evidence you need, including the exact hostname, error message, other working sites, resolver, query type, answer, and time. Propose two explanations and a safe test to distinguish them. This exercise builds the most valuable troubleshooting habit: testing a specific hypothesis and changing only what the results support.
Official Standards And Further Reading
The foundational DNS specifications are RFC 1034: Domain Names, Concepts and Facilities and RFC 1035: Domain Names, Implementation and Specification. They explain the namespace, delegation, resource records, servers, and resolvers. These standards are historical foundations, not a complete description of every later extension.
For encrypted DNS, consult RFC 8484 for DNS over HTTPS and RFC 7858 for DNS over TLS. For DNSSEC concepts, read RFC 4033. The ICANN website offers additional information on domain registration and the naming ecosystem.
This guide explains the stable principles of DNS. Specific operating-system menus, browser defaults, provider dashboards, and supported commands can change. Consult current vendor documentation when applying changes to production systems. The safest approach is to distinguish the authoritative record from the cached answer, the lookup from the network connection, and a technical success from a security guarantee.
Frequently Asked Questions
What Does DNS Stand For?
DNS stands for Domain Name System, a distributed system for publishing and retrieving information associated with domain names.
Is DNS The Same As An IP Address?
No, DNS provides naming information, while an IP address identifies a network-layer destination.
Does Changing DNS Improve Wi-Fi Speed?
Not necessarily, because it can affect lookup latency but cannot repair wireless signal quality or increase broadband bandwidth.
What Is A DNS Cache?
A DNS cache stores recent lookup answers for a limited period to avoid repeated queries.
What Does NXDOMAIN Mean?
It indicates that the queried name does not exist in the DNS answer returned by the resolver.
What Is An AAAA Record?
An AAAA record associates a DNS name with an IPv6 address. An A record carries an IPv4 address.
Why Do DNS Changes Take Time?
Resolvers can continue serving previously cached answers until their permitted lifetimes expire.
Is DNSSEC The Same As Encrypted DNS?
No, DNSSEC authenticates signed DNS data, while DoH and DoT encrypt traffic to a resolver.
Can DNS Work When A Website Is Down?
Yes, DNS may return an address even when the web server or application fails.
Should I Flush DNS For Every Website Error?
No, you should flush a cache only when evidence points to stale local lookup data. It will not repair unrelated network or server faults.



