How to Check Whether Your Domain's Nameservers Point Where You Think They Do
Your site can point at the wrong server for days without anyone noticing. Here is how to check your nameservers against what your host expects, in minutes.
You moved your site to a new host, you updated the nameservers, and everything looks fine from your desk. Then a customer in another country says your site still shows the old one, or your email stops arriving, and you start wondering whether the change ever took. That is the nameserver problem in a nutshell: the setting lives in a place you rarely look, and when it is wrong, the symptoms show up everywhere except where you are looking.
I check nameservers the same way every time, and it takes about five minutes. You need two things: what your nameservers are supposed to be, and what the rest of the internet actually sees. If those two lists match, you are done. If they do not, the difference tells you exactly where to look next.
Nameservers live in two places, and that is where the confusion starts
Here is the part most guides skip. Your nameservers are recorded in two different places, and they can disagree with each other.
The first place is the registry, the ledger for your domain's ending. When you set nameservers at your registrar, the registrar sends them to the registry, and the registry tells the rest of the internet where your domain's DNS lives. This is the delegation, and it is what a WHOIS lookup shows you.
The second place is inside your own DNS zone. Your DNS provider also publishes NS records in the zone it hosts. Normally the two lists match exactly, but nothing forces them to. When they drift apart, you get the kind of fault that looks different from every angle and drives people mad.
So a proper check reads both. One source alone can lie to you by being out of date.
Step 1: Find out what your nameservers should be
Before you check anything, write down the nameservers your host or DNS provider gave you. They usually look like a pair of hostnames, something like ns1.examplehost.com and ns2.examplehost.com. You will find them in your hosting account under a heading like Plan Details, Domains, or DNS Management, or in the welcome email from when you signed up.
Keep that list in front of you. The whole check is a comparison, and comparing from memory is how a wrong value slips past. I keep mine in a note next to the domain, because six months from now I will not remember which pair I set.
Step 2: Check what the registry actually has
Now run your domain through our WHOIS Lookup and look for the Name Server lines. This is the delegation, the answer straight from the registry. It is especially useful right after a change, because it shows what your registrar has actually filed, not what some resolver happens to have cached.
Then run the same domain through our DNS Records Lookup and read the NS records. That is the live answer, what the name servers are returning right now.
Here is a real example, from this very site. A lookup on websmartools.com returns two nameservers, roan.ns.cloudflare.com and tori.ns.cloudflare.com, with a TTL of 21600 seconds, which is six hours. Both the WHOIS record and the live DNS answer agree on that pair, so the delegation is healthy. That is what a clean result looks like: same names, both places, no surprises.
If you run your own domain and the two lists match each other and match the pair your host gave you, stop here. Your nameservers are right, and whatever problem you are chasing lives somewhere else.
Step 3: Read the result when the lists disagree
A mismatch is not one problem, it is three possible ones, and which one you have depends on where the disagreement sits.
If the WHOIS record still shows the old nameservers, your registrar change has not reached the registry yet, or it never went through. Log back into your registrar and confirm the change actually saved. I have watched people type new nameservers into a form, close the tab, and never press save. It happens more than anyone admits.
If the WHOIS record shows the new nameservers but the live DNS lookup still shows the old ones, you are probably looking at caching. Resolvers around the world hold the old answer until its TTL expires, and with a TTL of six hours or a full day, that wait is real. Our DNS Propagation Checker asks resolvers in several countries at once, so you can see the old answer dying off region by region instead of guessing.
If the two lists disagree in a way that never converges, even after a day, something is genuinely misconfigured. The most common cause is DNSSEC. If DNSSEC is switched on at your old registrar and the new setup does not carry it over, resolvers can refuse the new answers entirely. The fix is to switch DNSSEC off at the registrar before the move, or set it up properly at the new provider, and then wait for the old signatures to expire.
The mistake I see most often
People edit DNS records at the wrong company. They add an A record at their old host, or at their registrar's DNS editor, while the domain's nameservers still point somewhere else entirely. Those records sit in a zone nobody is asking, so nothing changes, and the person concludes DNS is broken.
The rule is simple: DNS records only matter in the zone your nameservers point to. If your nameservers say Cloudflare, your records must live in Cloudflare. If they say your host, the records must live at your host. Before you touch any record, check where the nameservers point. Our post on checking your DNS records before changing nameservers walks through the full safety check for exactly this reason.
What to do first
Run your domain through the DNS Records Lookup and the WHOIS Lookup right now, and compare the two NS lists against the pair your host gave you. If all three agree, your nameservers are not your problem, and you have just ruled out the most confusing suspect in five minutes. If they disagree, you now know whether the fault is at the registrar, in a cache, or in a zone nobody is reading, and that is a much shorter fix than the blind troubleshooting you were about to do.
A new post lands here every day. If there is a topic you want covered, email ask@websmartstudios.com.