Why use this tool instead of pinging the domain or checking it in the browser?

Your browser and ping go through whichever resolver your OS is set to (your ISP, 1.1.1.1, 8.8.8.8, NextDNS, etc.), and those resolvers plus the browser cache layer hold answers for the record's TTL. This tool runs the query from the packet.guru server using dig, which bypasses your local browser and OS caches entirely. The result is still subject to short-lived caching on the server side, but it is a fresher answer than waiting for your local caches to expire after a DNS change.

Which DNS records can I check with this tool?

This tool handles the three most common types: A (IPv4 address), AAAA (IPv6 address), and CNAME (an alias that points to another name). For other record types use a dedicated page: MX Lookup, TXT Lookup, or NS Lookup.

My query returns NXDOMAIN. What does that mean?

NXDOMAIN means "non-existent domain": the authoritative nameserver says no record of this name exists. Common causes: a typo in the domain, the domain expired, the DNS zone was deleted, or you're asking for a record type the domain just doesn't have set (try a different record type to confirm the domain itself resolves). If your domain was registered just now, give it a few minutes, since registrars publish zones in batches.

How long until my DNS change takes effect everywhere?

Technically the change is live the moment it's published on the authoritative nameserver. The waiting you feel is caching: resolvers around the world (including your ISP, your browser, your OS) still hold the old answer until its TTL expires. Typical TTL is anywhere from 5 minutes to 24 hours. This tool queries from the packet.guru server, which has its own short-lived resolver cache, so it will usually show the new record faster than your local stack does.

Should I lower my TTL before a planned migration?

Yes. Drop the TTL to 300 seconds (5 minutes) at least 24 to 48 hours before you change the record. Resolvers cache the record for whatever TTL they last saw, so the day before migration they'll cache a 5-minute version, then expire it quickly when you flip the record. After the migration settles, raise TTL back up (3600 or more) to reduce DNS query load on your nameservers.

Why can't I put a CNAME on my apex domain like example.com?

The DNS spec forbids a CNAME at the apex (the bare domain without a subdomain), because the apex must carry other records like SOA and NS, and a CNAME doesn't allow coexisting records on the same name. Workarounds: use an A or AAAA record pointing directly to an IP, use ALIAS/ANAME if your DNS provider supports it (Cloudflare, Route 53, DNSimple do), or keep the apex on an A record and put the canonical site on www.example.com via redirect.

Why might two people see different IPs for the same domain?

Many large services use geo-aware DNS: a CDN like Cloudflare or Akamai answers a query with the IP of the edge server closest to the resolver that asked. Your friend in another country gets a different IP, both correct. This is also how load balancing across regions works. Because this tool queries from the packet.guru server, you typically see the IP block for the server's region, not your own. To see what a specific country sees, you would need a resolver in that region.

Yes, it's free, no signup, no ads. Requests are rate-limited per IP to keep things fair.

DNS

DNS Lookup

Resolve domain to IP

Input

Run a DNS query from the packet.guru server using dig, bypassing your local browser and OS cache. Retrieves A, AAAA, and CNAME records.

Terminal

Console ready. Execute a command to see output...

About DNS Lookup

The Phonebook of the Internet

Computers don't speak English, they speak numbers. DNS (Domain Name System) is the translator that turns a domain name into an IP address.

Record Types You'll See

A Record: "Address". The fundamental map to an IPv4 server.
AAAA: The modern IPv6 address (future-proofing).
CNAME: "Canonical Name". A forwarding address. "Go ask that domain instead."

Classic DNS queries cross the network unencrypted, so your ISP or the Wi-Fi operator can read every name you look up. DoH, DoT and DoQ are the ways to close that.

How to use DNS Lookup

Enter the domain
Type the domain name (like example.com) into the field. No http:// and no trailing slash.
Pick the record type
Choose A for an IPv4 address, AAAA for IPv6, or CNAME for an alias. Other record types live in their own tools: MX Lookup, TXT Lookup, NS Lookup.
Run the lookup
Hit the Lookup button. The query runs from the packet.guru server via dig, bypassing your browser and OS cache. The answer reflects what the server currently sees, which is usually fresher than your local stack.
Read the result
Each line in the terminal panel is a record value. Copy what you need, or switch the record type and look up again to dig further. To check whether this record has spread to resolvers worldwide, use the DNS Propagation Checker.

Frequently Asked Questions

: Your browser and ping go through whichever resolver your OS is set to (your ISP, 1.1.1.1, 8.8.8.8, NextDNS, etc.), and those resolvers plus the browser cache layer hold answers for the record's TTL. This tool runs the query from the packet.guru server using dig, which bypasses your local browser and OS caches entirely. The result is still subject to short-lived caching on the server side, but it is a fresher answer than waiting for your local caches to expire after a DNS change.
: This tool handles the three most common types: A (IPv4 address), AAAA (IPv6 address), and CNAME (an alias that points to another name). For other record types use a dedicated page: MX Lookup, TXT Lookup, or NS Lookup.
: NXDOMAIN means "non-existent domain": the authoritative nameserver says no record of this name exists. Common causes: a typo in the domain, the domain expired, the DNS zone was deleted, or you're asking for a record type the domain just doesn't have set (try a different record type to confirm the domain itself resolves). If your domain was registered just now, give it a few minutes, since registrars publish zones in batches.
: Technically the change is live the moment it's published on the authoritative nameserver. The waiting you feel is caching: resolvers around the world (including your ISP, your browser, your OS) still hold the old answer until its TTL expires. Typical TTL is anywhere from 5 minutes to 24 hours. This tool queries from the packet.guru server, which has its own short-lived resolver cache, so it will usually show the new record faster than your local stack does.
: Yes. Drop the TTL to 300 seconds (5 minutes) at least 24 to 48 hours before you change the record. Resolvers cache the record for whatever TTL they last saw, so the day before migration they'll cache a 5-minute version, then expire it quickly when you flip the record. After the migration settles, raise TTL back up (3600 or more) to reduce DNS query load on your nameservers.
: The DNS spec forbids a CNAME at the apex (the bare domain without a subdomain), because the apex must carry other records like SOA and NS, and a CNAME doesn't allow coexisting records on the same name. Workarounds: use an A or AAAA record pointing directly to an IP, use ALIAS/ANAME if your DNS provider supports it (Cloudflare, Route 53, DNSimple do), or keep the apex on an A record and put the canonical site on www.example.com via redirect.
: Many large services use geo-aware DNS: a CDN like Cloudflare or Akamai answers a query with the IP of the edge server closest to the resolver that asked. Your friend in another country gets a different IP, both correct. This is also how load balancing across regions works. Because this tool queries from the packet.guru server, you typically see the IP block for the server's region, not your own. To see what a specific country sees, you would need a resolver in that region.
: Yes, it's free, no signup, no ads. Requests are rate-limited per IP to keep things fair.