How to check which DNS a domain is actually using

Whichever nameservers a domain uses right now determine where its DNS records are actually managed — and that is not always the company you expect, or the one showing in a control panel you assumed was authoritative. Before editing any record, checking this directly takes under a minute and avoids the single most common DNS mistake: changing a record somewhere that is quietly being ignored.

This matters more than it might seem, because nothing in either control panel warns you when this happens. A registrar's DNS editor is perfectly happy to let you add, edit, and save records against a domain whose nameservers point somewhere else entirely — the page will not grey out, no error will appear, and the change will sit there looking correct indefinitely, simply never being consulted by anything on the internet. The only way to know for certain is to ask the domain directly, rather than trusting whichever panel you happen to have open.

Checking the nameservers

On macOS or Linux:

dig +short NS yourdomain.com

On Windows:

nslookup -type=ns yourdomain.com

Whatever hostnames come back are authoritative for the domain right now, regardless of what any control panel implies. If they match your hosting provider, records are managed in your hosting control panel. If they match your registrar's own nameservers, records are managed at the registrar instead. If they match neither, the domain is using a third-party DNS service, and that is where records need to be edited. See what nameservers are for what this actually controls.

It is worth reading the whole result rather than the first line. Domains commonly list two to four nameservers, and while it is unusual, it is not impossible to find a mix — a leftover nameserver from a previous provider sitting alongside a new one, for instance, left over from an incomplete change. A mixed list like that is itself worth investigating, since it can mean different resolvers around the world are being handed genuinely different answers for the same domain, which produces exactly the kind of "it works for me but not for my colleague" symptom that is otherwise hard to explain.

Checking a specific record, once you know where it lives

Once you know which nameservers are authoritative, you can query any individual record directly against them, which shows you exactly what that specific nameserver is currently answering with — useful when a change has been made in one place but you suspect it has not spread everywhere yet.

dig +short A yourdomain.com @ns1.example-host.com

Replace the nameserver at the end with one of the actual hostnames returned by the NS lookup above. Querying a specific nameserver directly bypasses your own resolver's cache entirely, which makes it the fastest way to confirm whether a change has actually been saved, independent of how long it takes to spread everywhere else.

Checking from outside your own network

Your own connection almost always has a cached answer sitting in front of it — your router, your ISP's resolver, sometimes your operating system too. An online global DNS checker tool queries resolvers in a number of countries at once and shows you a map of who has picked up a given answer and who has not, which is a much more useful picture than repeatedly querying from the same network.

Why a domain might not use the nameservers you expect

• It was never changed after a migration. Moving hosting does not automatically update nameservers — that is a separate, deliberate step.
• A previous developer or agency set up third-party DNS. Services like a CDN, a dedicated DNS provider, or a specific application's own DNS management sometimes take over nameservers as part of their own setup.
• The domain was registered somewhere different from where it is hosted. Registration and hosting have never had to be with the same company, and a registrar's default nameservers are sometimes left in place by accident even after hosting moved elsewhere.

What to do once you know

Log in to whichever service the nameservers actually point at, and make your changes there. If that turns out not to be where you expected, and you would rather consolidate DNS management with your hosting provider, see how to point a domain to your hosting for switching over, or how to use external DNS with your hosting if you specifically want to keep DNS elsewhere while hosting the site with us.

If the result of a lookup does not make sense to you, or does not match anything you recognise, contact our support team with the domain name and we can help interpret what it is currently showing.