How does DNS work — and what does "pointing a domain" mean?

You type your domain into a browser, expect your site to appear, and instead you get a blank page, the wrong site, or a mystery error like ERR_NAME_NOT_RESOLVED.

Short version: DNS, short for Domain Name System, is the internet’s address book. It turns a human name like example.com into a server address that computers can reach. “Pointing a domain” means changing DNS records so your domain leads visitors to the server where your website or app lives.

How does DNS work?

DNS is like asking for directions before you drive somewhere.

You know the place by name: example.com. Your browser needs the actual address: usually an IP address, which looks like 203.0.113.10 or a longer IPv6 address. DNS is the system that answers, “Where should this name go?”

The journey usually has a few stops:

Your browser asks a DNS resolver. That resolver is often run by your internet provider, your router, or a service like Google Public DNS or Cloudflare DNS.

If the resolver does not already know the answer, it asks the wider DNS system. It finds which nameservers are responsible for your domain. A nameserver is the place that holds the official DNS records for that domain.

The nameserver replies with a record, such as an A record that says, “example.com goes to this IP address.” Your browser can then contact the server at that address.

So DNS does not serve your website. It only tells the browser where to go. Think of it as the street sign, not the building.

What does pointing a domain mean?

Pointing a domain means updating DNS so a name leads to the right server.

If you bought a domain from one company and your website lives on a server somewhere else, the domain does not magically know that. You have to connect the label to the destination.

The most common version is an A record:

example.com → your server’s IPv4 address

You may also point www.example.com, because www is a separate name. Many people forget this and end up with the main domain working while the www version fails, or the other way around.

There is one more important piece: DNS gets the visitor to the front door, but the server still has to know what to do when they arrive.

Imagine an apartment building. DNS gives the taxi driver the building address. Your web server decides which apartment door to open for example.com, blog.example.com, or shop.example.com. If the server is not set up for that domain, visitors may see a default page, another project, or a certificate warning.

If you want the practical version of this setup, see how to point a domain at your server. If the site still does not load after DNS looks right, the problem may be in another layer; this guide to why your website is not loading breaks that down.

Which DNS records matter most?

Most small websites only need a few DNS record types.

An A record points a name to an IPv4 address. This is the classic “send this domain to this server” record.

An AAAA record does the same thing for IPv6 addresses. Not every setup needs one, but if you add it, it must point to a server that is actually ready to answer over IPv6.

A CNAME record points one name to another name. For example, www.example.com can point to example.com. It is like saying, “Ask over there instead.”

An MX record tells email where to go. Changing your website records should not require changing MX records unless you are also moving email. This matters because a site can work perfectly while email is broken, or email can work while the site is broken.

A TXT record stores text used for verification and security. Services often ask you to add a TXT record to prove you own the domain.

An NS record says which nameservers are in charge of your domain. This is like choosing which office keeps the official map. If your NS records point to one provider, but you edit DNS at another provider, your changes will not matter.

DNS also has TTL, short for “time to live.” TTL tells resolvers how long they may keep an old answer before asking again. A long TTL can make DNS changes feel slow, because some visitors are still being sent to the old place for a while.

Why do DNS changes take time?

DNS changes are not always instant because the internet remembers old answers.

When a resolver asks for your domain, it often keeps the answer for the TTL period. That is useful because it makes browsing faster. Without caching, every page visit would need fresh directions from the start.

But caching can be annoying during a move. You update the A record, your phone sees the new site, your laptop still sees the old one, and a friend in another country sees something else. That does not always mean you did anything wrong. Different resolvers may be holding different cached answers.

The usual failure modes are more ordinary than they feel:

The A record points to the wrong IP address.

The www name was never created.

The NS records point to different nameservers than the place you edited.

The server receives the request but is configured for another domain.

HTTPS is not ready yet, so the browser shows a certificate warning. If that is the part you are stuck on, read how to get free HTTPS on your server.

DNS is simple in concept, but small mismatches can create confusing symptoms.

The shortcut

Server Manager helps by keeping the domain, the server destination, and the website’s public address lined up as one understandable setup. That spares you the common mess: a domain pointing to the wrong IP address, www forgotten, a project answering for the wrong name, or HTTPS failing because the certificate does not match the domain.

The real benefit is not that DNS becomes magic. It is that the setup stays legible. Months later, you can still understand which domain belongs to which project and what public address it is meant to use.

That matters most when you host more than one site. One change should not accidentally send visitors to another project or leave you guessing which old DNS edit caused the problem.

FAQ

Is DNS the same as hosting? No. DNS tells browsers where to go. Hosting is the server that actually runs your website or app.

Do I need both example.com and www.example.com? Usually, yes. They are separate names, so you should decide where each one goes.

Why does my domain work for me but not for someone else? Different DNS resolvers cache answers for different lengths of time. One person may see the new record while another still sees the old one.

What does ERR_NAME_NOT_RESOLVED mean? It usually means the browser could not turn the domain into an address. The DNS record may be missing, wrong, or not visible from that resolver yet.

What changes once DNS clicks?

Once you understand DNS, “pointing a domain” stops feeling like a ritual. You know you are connecting a readable name to a server address, then making sure the server is ready to answer for that name.

That gives you a calmer way to troubleshoot: check the name, check the records, check the destination, then check the website. The win is simple: your domain leads visitors to the right place, and you understand why.