DNS Lookup

What is DNS lookup?

DNS (Domain Name System) translates human-readable domain names like example.com into IP addresses like 93.184.216.34 that computers use to locate servers. A DNS lookup queries DNS servers to find these records. This tool performs DNS lookups and displays all record types associated with a domain, helping you troubleshoot connectivity issues and verify DNS configuration.

DNS is often called the phonebook of the internet. When you type a URL in your browser, your computer queries a DNS resolver (usually operated by your ISP or a service like Google's 8.8.8.8 or Cloudflare's 1.1.1.1) to find the IP address of the server hosting that website. This process happens transparently in milliseconds for every website you visit.

DNS record types

• A record — maps a domain to an IPv4 address. The most fundamental DNS record.
• AAAA record — maps a domain to an IPv6 address.
• CNAME record — creates an alias pointing one domain to another domain name.
• MX record — specifies the mail server responsible for receiving email for the domain.
• TXT record — holds arbitrary text, commonly used for domain verification and email authentication (SPF, DKIM, DMARC).
• NS record — identifies the authoritative nameservers for the domain.

How to use this tool

Enter a domain name and select the record type you want to look up (or choose All to see all records). The tool queries DNS servers and displays the results including the record value, TTL (time to live), and the responding nameserver. Use this to verify DNS changes have propagated, troubleshoot email delivery issues, or check domain configuration.

DNS propagation

When you change DNS records, the changes do not take effect instantly worldwide. DNS resolvers cache records for the duration specified by the TTL (Time to Live) value. A TTL of 3600 means resolvers will cache the old record for up to one hour. Full global propagation can take 24-48 hours in some cases. Before making changes, lower the TTL to reduce propagation time.

Example in practice

Query example.com and you typically get an A record pointing to an IPv4 address, an AAAA record for IPv6, MX records naming the mail servers, and NS records listing the authoritative name servers. A TTL of 3600 next to a record means resolvers may cache it for one hour. Reading these together confirms where a domain's website and email are actually hosted.

Common mistakes

A common misunderstanding is expecting a DNS change to take effect instantly. Resolvers cache records until the TTL expires, so a record with a 24-hour TTL can linger for a day. Lowering the TTL a few days before a planned migration avoids this. Another mistake is forgetting that a missing MX record means mail falls back to the A record, which is rarely what you want.

Frequently asked questions

Why is my DNS not working?

Common DNS issues include: incorrect A record IP address, missing MX records causing email failures, CNAME records conflicting with other record types at the root domain, and stale cached records after a change. Use this tool to verify your records are correct, then wait for TTL-based propagation. Clearing your local DNS cache (flushing) can also help.

What DNS server should I use?

Popular public DNS servers include Google (8.8.8.8), Cloudflare (1.1.1.1), and Quad9 (9.9.9.9). They are typically faster and more reliable than ISP-provided DNS. Cloudflare focuses on speed and privacy. Quad9 adds malware domain blocking. Google offers extensive infrastructure. All three are free and easy to configure on any device.

What is the difference between an A record and a CNAME?

An A record maps a name directly to an IP address. A CNAME maps one name to another name (an alias), which is then resolved to an IP. Use a CNAME to point "www" at your root domain, but never place a CNAME on the root domain itself — the standard forbids it.