dns2.seo.header
dns2.seo.description1
dns2.seo.description2
dns2.seo.cta
dns2.seo.description3
google.com
cloudflare.com
monsite.fr
dns2.seo.description4
$ checkhost monitor --type dns --interval 30s
Need continuous dns monitoring?
Monitor 24/7 from 15 locations. Instant alerts on Telegram, Discord, Slack & more.
About
DNS Lookup Tool — Check DNS Resolution Globally
DNS (Domain Name System) is the internet's address book — it translates human-readable domain names like google.com into IP addresses like 142.250.80.46 that computers use to connect. A DNS lookup queries DNS servers to find these records. CheckHost performs DNS lookups from multiple global nameservers simultaneously, showing you how your domain resolves from different parts of the world. This is essential for verifying DNS configurations, detecting propagation delays after changes, identifying geo-DNS routing, and troubleshooting resolution failures. Our DNS checker tests against authoritative and recursive resolvers worldwide, reporting the resolved IP addresses, TTL (Time-To-Live) values, and response times. If you're using a CDN like Cloudflare, you'll see different IPs from different locations — that's normal and expected with anycast DNS. If IPs are inconsistent when they shouldn't be, your DNS may still be propagating or there's a misconfiguration.
Usage
How to Perform a DNS Lookup With CheckHost
Enter a domain name (e.g., example.com, sub.domain.com) in the search field. Do not include http:// or https://.
Select 'DNS' from the tool tabs and click Check to query DNS resolvers worldwide.
Review results: each row shows a location, the resolved IP address(es), TTL values, and the resolver used.
If all locations resolve to the same IP, your DNS is consistent. If IPs differ, you're likely using a CDN or geo-DNS (which is intentional) or DNS hasn't fully propagated yet.
For detailed propagation tracking across record types (A, AAAA, CNAME, MX, TXT, NS), use our DNS Propagation tool.
FAQ
Frequently Asked Questions
Why do different locations resolve to different IP addresses?
This is normal if you use a CDN (Cloudflare, AWS CloudFront, etc.) or geo-DNS. These services intentionally return different IPs to route users to the nearest server. If you recently changed DNS records, some locations may show old values until propagation completes (typically 15 minutes to 48 hours depending on TTL).
How long does DNS propagation take?
DNS propagation typically takes 15 minutes to 48 hours, depending on the TTL (Time-To-Live) set on your records. Records with short TTLs (300s = 5 min) propagate faster. Most changes propagate within 1-4 hours. To speed up propagation: lower your TTL to 300 seconds at least 24 hours before making changes, then make the change, then raise TTL back.
What are common DNS record types?
A = IPv4 address (most common). AAAA = IPv6 address. CNAME = Alias pointing to another domain. MX = Mail server (for email delivery). TXT = Text records (used for SPF, DKIM, domain verification). NS = Nameserver records (which DNS servers are authoritative). SOA = Start of Authority (domain metadata). CAA = Certificate Authority Authorization (which CAs can issue SSL).
What does NXDOMAIN mean?
NXDOMAIN (Non-Existent Domain) means the domain name doesn't exist in DNS. This could mean: the domain isn't registered, the domain has expired, nameservers aren't configured, or you've queried a subdomain that doesn't have a DNS record. Check the domain registration status with our WHOIS tool.
What DNS resolver does CheckHost use?
CheckHost queries through multiple resolvers including Google Public DNS (8.8.8.8), Cloudflare DNS (1.1.1.1), and local ISP resolvers at each testing location. This gives you a realistic picture of how your domain resolves for actual users worldwide, not just from one resolver's perspective.