TinyPingTinyPing

DNS Lookup

Look up every common DNS record for a domain in one go: A, AAAA, CNAME, MX, TXT, NS, CAA and SOA, each with its TTL. Enter a domain or hostname such as example.com or www.example.com.

Common DNS problems

The domain returns no records at all

Check the NS records first. If they point to a DNS provider where the zone does not exist, or the domain has expired and the registrar removed its nameservers, nothing resolves. Confirm the nameservers at your registrar match the provider where you edit records.

You changed a record but still see the old value

Resolvers keep an answer for the TTL that was set when they fetched it. If the old record had a TTL of 3600, some visitors can see it for up to an hour. Lower the TTL a day before a planned change, then raise it again afterwards.

You edited records at the wrong provider

Only the provider named in the NS records answers for your domain. After moving to Cloudflare, for example, edits made in your registrar's or old host's DNS panel have no effect. Compare the NS records shown here with where you are editing.

The site has an IPv6 (AAAA) record that does not work

Visitors on IPv6 networks connect to the AAAA address first. If it points to an old server or one that does not listen on IPv6, those visitors get errors while everyone else is fine. Fix the address or remove the AAAA record.

Certificate issuance fails because of CAA

A CAA record lists which certificate authorities may issue for the domain. If it names only one CA and your host uses another (Let's Encrypt, Google Trust Services, Sectigo), issuance is refused. Add the CA your platform uses, or remove the CAA record.

How to look up DNS records

  1. Enter a domain such as example.com, or a full hostname such as shop.example.com.
  2. Click Look up DNS.
  3. Read each record type with its value and TTL. NS tells you which provider answers for the domain.
  4. After a change, wait for the old TTL to pass and look again.

What is a DNS lookup?

DNS (Domain Name System) turns names like example.com into the information computers need: IP addresses, mail servers, verification tokens and more. A DNS lookup asks a resolver for the records stored under a name and shows what comes back.

Each record has a type. A and AAAA hold IPv4 and IPv6 addresses. CNAME makes a name an alias of another name. MX lists the servers that receive email. TXT holds free text, used for SPF, DMARC and domain verification. NS names the authoritative nameservers. CAA limits which certificate authorities may issue certificates. SOA holds zone details such as the serial number.

Every record also has a TTL (time to live): how many seconds resolvers may cache it. That cache is why DNS changes are not instant everywhere.

This tool asks public resolvers over DNS-over-HTTPS (Cloudflare 1.1.1.1, with Google 8.8.8.8 as a fallback). You see what the public internet sees, not what your own computer or router has cached. It is one view from public resolvers, not a check from many locations around the world.

example.com.  3600  IN  A      203.0.113.10
example.com.  3600  IN  MX     10 mail.example.com.
example.com.  3600  IN  TXT    "v=spf1 include:_spf.google.com ~all"
example.com.  86400 IN  NS     ns1.example-dns.com.

When to use a DNS lookup

After moving DNS to Cloudflare or Route 53

Confirm the NS records point to the new provider and that the A, MX and TXT records you rely on came across.

Launching a site on a new host

Check that the A or CNAME record now points to the new server or platform, and that no stale AAAA record still points to the old one.

Setting up Google Workspace or Microsoft 365

See the MX and TXT records side by side to confirm mail routing and the verification token are in place before you switch over.

Debugging "it works for me"

If a site loads for you but not for a customer, compare the public answer here with what your machine resolves. A local cache or hosts file entry is a common cause.

Check something else

Frequently asked questions

How long does DNS propagation take?

A changed record reaches everyone once the old TTL has expired in the caches that hold it, usually minutes to a few hours. Nameserver changes at the registrar can take up to 48 hours because the parent zone's NS records have long TTLs.

Does this tool check DNS propagation worldwide?

No. It asks public resolvers (Cloudflare, with Google as fallback) and shows their answer. That is a good indication of what new visitors see, but it is not a test from many locations.

Why do I see different results on my computer?

Your operating system, browser and router cache DNS answers, and your ISP's resolver has its own cache. A hosts file entry or a VPN can also change the answer. Flush your local DNS cache or wait for the TTL to pass.

What TTL should I use?

300 to 3600 seconds suits most records. Use a short TTL such as 300 before a planned migration so changes take effect quickly, and a longer one for records that rarely change.

Why are there no A records for my domain?

The domain may use a CNAME on www only, the apex may never have been pointed anywhere, or the nameservers may not have the zone. Check the NS records, then the records at that provider.

What does the SOA serial number mean?

It is a version number for the zone. Many providers increase it on every change, which lets secondary nameservers know they need to update. Some managed DNS providers do not change it in a meaningful way.

Stop checking DNS by hand

A deleted record, an expired domain or a botched nameserver move takes a site offline without warning. TinyPing checks your site every 5 minutes and alerts you when:

  • the domain stops resolving
  • the site returns an error or times out
  • an expired certificate breaks HTTPS
Start monitoring free for 7 days

US$6.99 a month or US$47 a year per 50 monitors, team members free. 7-day free trial, no card needed.

Want alerts in team chat? Follow the guide for Slack or Google Chat.