DNS Lookup

What is DNS?

The Domain Name System (DNS) is often called the phonebook of the internet. It translates human-readable domain names like example.com into machine-readable IP addresses like 93.184.216.34. Without DNS, you would need to memorise IP addresses for every website you visit.

When you type a domain into your browser, a chain of lookups happens behind the scenes. Your device first checks its local cache, then asks a recursive resolver (usually provided by your ISP or a public resolver like Cloudflare 1.1.1.1 or Google 8.8.8.8). The recursive resolver queries the DNS hierarchy: starting at the root servers, then the TLD servers (e.g. .com, .uk), and finally the authoritative nameservers for the specific domain. The answer is cached at each level for the duration specified by the TTL.

DNS Record Types

DNS supports many record types, each serving a different purpose:

• A — Maps a domain to an IPv4 address. The most fundamental record type, used for website hosting.
• AAAA — Maps a domain to an IPv6 address. Essential for modern internet connectivity as IPv4 addresses become scarce.
• CNAME — Creates an alias from one domain to another. Cannot coexist with other record types at the same name.
• MX — Specifies mail servers for the domain with priority values. Essential for email delivery.
• TXT — Holds arbitrary text data. Commonly used for domain verification, SPF records, DKIM keys, and DMARC policies.
• NS — Identifies the authoritative nameservers for the domain. These are the servers that hold the definitive DNS records.
• SOA — Start of Authority record containing zone metadata: primary nameserver, admin contact, serial number, and refresh/retry/expiry timers.
• CAA — Certificate Authority Authorization specifies which certificate authorities are permitted to issue SSL/TLS certificates for the domain.
• SRV — Service record that specifies the host, port, priority, and weight for specific services like SIP, XMPP, or LDAP.

Understanding TTL

Time To Live (TTL) is a value in seconds that tells resolvers how long to cache a DNS record before requesting a fresh copy from the authoritative server. TTL directly affects how quickly DNS changes propagate across the internet.

• Short TTL (60-300 seconds) — Changes propagate within minutes. Ideal before planned migrations or for DNS-based failover. The trade-off is increased DNS query volume.
• Medium TTL (3600 seconds / 1 hour) — A common default. Good balance between propagation speed and caching efficiency.
• Long TTL (86400 seconds / 1 day) — Best for records that rarely change. Reduces DNS traffic and improves resolution speed for end users.

A common best practice is to lower TTL values to 300 seconds a day or two before making DNS changes, then raise them back after the change has been confirmed.

How to Use DNS Lookup

Our DNS lookup tool queries authoritative servers directly for accurate, real-time results. Here are some practical use cases:

• Check propagation — After making a DNS change, use this tool to verify the new record is live. If you still see old values, the TTL of the previous record may not have expired yet.
• Verify configuration — Before launching a website or configuring email, confirm that A, MX, and TXT records are set correctly.
• Troubleshoot issues — If a website is not loading or email is not arriving, checking DNS records is always the first diagnostic step.
• Use ALL type — Select ALL from the record type dropdown to query every record type at once and get a complete picture of a domain DNS configuration.