How to Check DNS Resolution
Check exactly what IP address or DNS record a domain is resolving to before you keep troubleshooting the wrong thing.
Before you start
When this guide is useful
If a website loads the old server or old environment, the first thing to confirm is the DNS answer being returned right now.
Checking DNS resolution tells you whether the new record is being returned yet or whether the old value is still active.
Comparing DNS answers is one of the fastest ways to see whether two devices are using different resolver results.
A direct DNS query gives you concrete evidence instead of guessing whether the problem is DNS, hosting, SSL, or application behavior.
Step-by-step instructions
1. Run a basic nslookup query
Start with a simple DNS query to see what answer your current resolver returns for the domain.
nslookup example.comCheck which IP address is returned and which DNS server answered the query.
2. Query a specific DNS server directly
If you want to compare results, query a known public resolver such as Google DNS directly.
nslookup example.com 8.8.8.8If your default resolver and a public resolver return different answers, you immediately know the difference is DNS-related rather than a browser-only issue.
3. Use dig for more detailed output
If dig is available on your system, use it when you want a cleaner and more detailed DNS response.
dig example.comIt makes it easier to inspect record sections, answer details, and TTL values during troubleshooting.
4. Query a specific resolver with dig
Just like nslookup, dig can also query a specific DNS server directly.
dig @8.8.8.8 example.comCompare this answer with your default resolver result to see whether propagation or resolver cache differences are still involved.
5. Check a specific record type when needed
If you are troubleshooting more than a basic A record, query the specific record type directly.
dig example.com Adig example.com CNAMESometimes the confusion is not about the final IP itself but about whether the domain should resolve through a CNAME, MX, TXT, or another record type.
6. Compare the answer with what you expected
Do not stop at the command output. Compare the returned value with the actual IP address, hostname, or record you intended to publish.
If the answer is wrong, the issue is likely DNS or propagation related. If the answer is correct but the site still fails, the problem is probably elsewhere such as web server config, firewall, or application routing.
Common mistakes
DNS propagation and resolver differences mean one server result may not match another at the same moment.
A correct DNS answer only proves the resolution is right. The website itself can still fail for unrelated reasons.
If you are troubleshooting the wrong record type, the lookup may technically work while still not answering the real question.
The command output is only useful if you know what answer you actually expected to see.
About this guide
This guide shows how to check DNS resolution when a domain points to the wrong server, does not pick up a recent DNS change, or behaves differently across devices and networks. It focuses on practical use of nslookup and dig so you can confirm exactly what IP address or record a domain is resolving to.
How to follow this guide
- Run a basic DNS lookup for the domain.
- Check which IP address or record is currently being returned.
- Query a specific DNS server if you need to compare answers.
- Use dig when you want more detailed DNS output.
- Compare the result with the expected DNS value before changing anything else.
Why use this method?
DNS problems are often misdiagnosed as general internet issues when the real problem is simply that a domain is resolving to the wrong destination. A direct DNS lookup tells you what answer the system or resolver is actually returning right now.
Frequently Asked Questions
What does DNS resolution mean?
It means converting a domain name such as example.com into the IP address or DNS record that the system uses to reach it.
Why would I check DNS resolution manually?
You should check it when a site points to the wrong server, a recent DNS change is not taking effect, or different devices return different results.
What is the difference between nslookup and dig?
Both query DNS, but dig usually gives more detailed output and is preferred for deeper troubleshooting.
Why do two DNS servers return different answers?
They may be using different caches, different propagation states, or different resolver policies at that moment.