Your domain isn't pointing to your server: DNS troubleshooting

You typed your domain, expected your site, and got the wrong page, a parking screen, or nothing at all.

Short version: when your domain is not pointing to your server, DNS is usually sending visitors to the wrong address, using the wrong nameservers, or still holding on to old records. Check the nameservers first, then the A record, AAAA record, and www record, and remember that DNS changes can take time to spread.

Think of DNS as the address book for the internet. Your domain is the name people remember; your server’s IP address is the street address where the site actually lives.

What does “domain not pointing to server” mean?

A domain does not “contain” your website. It points to the place where your website is hosted.

The usual pointer is an A record, which sends a domain like example.com to an IPv4 address such as 203.0.113.10. There may also be an AAAA record, which points to an IPv6 address. If either record points to the wrong place, some visitors may end up at the old host, a blank server, or a browser error.

There is also www.example.com. That is not automatically the same as example.com. It needs its own record, often a CNAME record, which acts like “send www wherever the main domain goes.”

So when someone says “my domain is not pointing to my server,” they usually mean one of these things:

• example.com points to the wrong IP address.
• www.example.com points somewhere different.
• The domain is using the wrong DNS provider.
• An old IPv6 record is quietly overriding the correct setup for some visitors.
• The site points correctly, but the web server or HTTPS setup is not ready.

If you are setting this up from scratch, our plain guide on how to point a domain at your server walks through the happy path.

Why is DNS still sending people to the wrong place?

The most common cause is simple: you edited DNS in the wrong place.

Your domain has nameservers. Nameservers are the official phone book for that domain. If your domain uses Cloudflare nameservers, but you edit records at your domain registrar, those changes may do nothing. It is like changing your address in an old notebook nobody uses anymore.

The second common cause is old records. Maybe the A record still points to your previous hosting company. Maybe www still points to a website builder. Maybe an AAAA record points to an old IPv6 address while the A record is correct. That last one is sneaky because some networks prefer IPv6, so the site may fail for one person and work for another.

The third cause is time. DNS has a waiting period called TTL, short for “time to live.” It tells networks how long they are allowed to remember an old answer before asking again. This is why a change can work on your phone but not on your laptop, or work in one country but not another.

This delay is often called DNS propagation. It is not really one big update spreading across the planet. It is more like lots of local address books slowly throwing away their old sticky notes.

How do you check where the domain is really going?

Start with the outside view. Do not only trust your browser, because browsers cache things and can remember old answers.

Check these pieces in order:

1. Nameservers — are they the ones you expect? If not, you are editing DNS in the wrong control panel.
2. A record for the root domain — does example.com point to your server’s IPv4 address?
3. AAAA record — if it exists, does it point to a valid IPv6 address on the same server? If you do not use IPv6, an old AAAA record can cause confusing failures.
4. www record — does www.example.com point to the same site as the root domain?
5. HTTPS certificate — if DNS is correct but the browser shows a certificate warning, the domain may be arriving at the right server before HTTPS is ready.

The literal symptoms can vary. You might see DNS_PROBE_FINISHED_NXDOMAIN, which usually means the domain cannot be found in DNS. You might see “This site can’t be reached,” which can mean DNS is wrong, the server is not answering, or a firewall is blocking traffic. You might see the wrong website, which usually means the domain is pointing somewhere, just not where you intended.

That distinction matters. “Not found,” “wrong place,” and “right place but not serving the site” are different problems. Our guide to why your website is not loading breaks those layers apart.

Also check both versions of the domain: with and without www. Many people fix one and forget the other. To visitors, they feel like the same address. To DNS, they are two separate labels.

FAQ

How long does DNS take to update? Often minutes, sometimes a few hours. In awkward cases, old cached answers can linger for up to a day or two depending on the previous TTL.

Do I need both an A record and a CNAME record? Usually the root domain uses an A record, while www uses a CNAME record pointing to the root domain. Do not create conflicting records for the same name.

Why does the domain work for me but not for someone else? Different networks cache DNS answers separately. Your connection may have the new address while someone else’s provider still remembers the old one.

Can HTTPS make it look like DNS is broken? Yes. If DNS points correctly but the certificate is missing, expired, or issued for the wrong name, the browser may block the page. See our guide to free HTTPS on your server.

The shortcut

Server Manager helps by keeping the domain, the server, and the site relationship visible in one place. That matters when the real issue is not mysterious at all: the root domain points correctly, www is forgotten, an old AAAA record is still hanging around, or HTTPS is attached to the wrong name.

The real benefit is that your setup stays legible months later. You are not trying to remember which DNS panel mattered, which address belonged to which project, or why one domain was treated differently from the others.

It also reduces the chance that one change breaks another site on the same server. When you host more than one project, clear domain mapping is the difference between “this one domain is wrong” and “I am afraid to touch anything.”

What does “fixed” look like?

A fixed domain is boring in the best way.

The root domain and www version both reach the right site. DNS checkers show the server address you expect. There are no old AAAA records sending part of your traffic elsewhere. HTTPS loads without warnings, and a visitor does not need to know which version of the address to type.

That is the win: your domain becomes a reliable front door again. People type the name, the internet finds the right server, and your site appears where it should.