How DNS works
DNS is the internet's translation layer: it turns domain names into the IP addresses computers actually connect to. This guide walks a lookup through the resolver, root, TLD and authoritative name servers, then covers the records you are likely to touch.
What is DNS, and why it exists
Computers reach each other by IP address; people use names. The Domain Name System (DNS) is the worldwide, distributed directory that maps names like example.com to numbers like 192.0.2.7. Nothing about a domain name requires a website — DNS simply answers the question "what address does this name point to?" for whatever is asking: a browser, a mail server, anything.
DNS is hierarchical and cached at every level, which is why it scales: no single server knows every name, and every answer travels with an expiry time so it can be reused.
How a domain name resolves to an IP address, step by step
When someone opens www.brightplumbing.com, the lookup runs roughly like this:
- Local caches first. The browser and the operating system each keep recent answers. If this name was resolved moments ago, the cached answer is used and nothing further happens.
- The recursive resolver. On a cache miss, the query goes to a resolver — the one your internet provider runs, or a public one such as those run by Cloudflare or Google. Its job is to chase the answer down on your behalf and cache it.
- The root servers. The resolver asks one of the DNS root servers. Root does not know plumbing sites, but it knows who runs
.com: it returns the TLD name servers. - The TLD name servers. The
.comservers know which name servers hold thebrightplumbing.comzone, and return those. - The authoritative name servers. These hold the actual record for
www.brightplumbing.com— the A record with its IP address — and return it. - The answer travels back, cached at each step, and the browser connects to the IP address and asks for the page.
The whole chain normally takes milliseconds, because of the caching: your resolver almost certainly has the .com servers cached already, and popular names are often answered straight from cache.
What is a name server?
A name server is a server that answers DNS questions for some set of names. The ones at step 5 — the authoritative name servers for your domain — are the servers you control through your registrar or DNS provider: they hold your domain's zone file, the list of records for the name and everything under it.
Every domain must list at least two name servers in its NS records at the parent zone. Changing a domain's name servers — from the registrar's defaults to a web host's, or to a dedicated DNS service — is how you hand control of the name's records to whoever you want. That single setting decides where the name points; until it changes, records you add at a new provider sit unused.
DNS records you will actually touch
- A — maps a name to an IPv4 address (
brightplumbing.com→192.0.2.7). The first record every site needs. - AAAA — the same, for an IPv6 address.
- CNAME — makes one name an alias of another (
www→brightplumbing.com), so the alias follows whatever the target points to. A CNAME cannot coexist with other records at the domain root, which is why providers document it for subdomains and services. - MX — directs mail for the domain to the right mail servers, with a priority number for ordering. This is the DNS record that determines the destination mail server for a domain.
- TXT — free-form text records, used mostly for verification and mail authentication: proving domain ownership to a service, publishing SPF and DKIM settings.
- NS — lists the name servers for the zone; changing these delegates the domain.
TTL and propagation
Every DNS record carries a TTL (time to live): how long, in seconds, others may cache the answer. Typical values run from a minute to a day. When you change a record, resolvers around the world keep serving the old answer until their cached copy expires — that gradual rollout is what people call propagation. There is no single switch and no fixed duration: the practical answer to "how long does it take for a DNS change to take effect" is "up to the old record's TTL, usually within a few hours." A common practice before planned moves is to lower the TTL in advance, make the change, and raise it again after traffic has shifted.
Subdomains and domain forwarding
A subdomain is any name under your registered domain: blog.brightplumbing.com, shop.brightplumbing.com. You create one simply by adding a record — there is nothing extra to register or pay for, and the same zone can point each subdomain somewhere different. Forwarding a domain or subdomain means sending visitors elsewhere: typically the name's records point at a forwarding service that issues a redirect to the target. Forwarding is how brightplumbing.net quietly sends people to brightplumbing.com.
What it means when a domain is parked
A parked domain is one that resolves but has no site: its records point to a placeholder page, often the registrar's "future home of" page or a page of ads. Newly registered names default to parked until you point them somewhere, and many names sit parked for years while their owners decide. Parking is also why an old-looking name can show ads today and a real site tomorrow.
Email on your own domain
Email for [email protected] is delivered using the domain's MX records: the sending mail server looks them up and hands the message to a server on the list. You do not run that server yourself — you point the MX records at an email provider, then add the TXT records (SPF, DKIM, DMARC) that let your outgoing mail be verified as genuinely yours. One consequence worth knowing: if the domain lapses, mail stops being delivered the moment its records do — see expired domain names.
Frequently asked questions
Why does registering a domain name include specifying DNS?
Because a registration alone points nowhere. The registry needs to know which name servers hold the name's records; without that, the name would not resolve at all — no site, no email. That is why every registrar asks for name servers at registration, and why "registered but pointed at the registrar's parking page" is the default state of a new name.
What happens when DNS is down?
Nothing can find the site: browsers report that the name cannot be resolved, and mail delivery is delayed or bounces as cached answers expire. The registration itself is unaffected — DNS being down deletes nothing — and service returns as soon as the name servers answer again.
What is the difference between DNS and a name server?
DNS is the whole system; a name server is one server within it. The difference is like that between the postal service and a post office.
How long does a DNS change take to show up everywhere?
Up to the TTL of the record you changed — minutes for short TTLs, up to a day or so for long ones — plus whatever caching happens above it. See TTL and propagation above.