DNS lookup

What is DNS Lookup?

DNS lookup is the fundamental process that makes the internet work. Every time you type a domain name into your browser, a DNS lookup happens behind the scenes to find the server hosting that website. The Domain Name System (DNS) acts as the internet's address book: it stores records that map domain names to IP addresses and other server information. Without DNS lookup, you would need to memorize the numerical IP address of every website you visit—something impractical given there are billions of websites online.

There are two types of DNS lookup. Forward DNS lookup translates a domain name (like example.com) into an IP address (like 93.184.216.34). Reverse DNS lookup does the opposite: it takes an IP address and returns the domain name associated with it. Reverse lookups are commonly used for email server verification and security audits. This tool performs forward DNS lookups, returning all the records that an authoritative nameserver holds for a domain.

When you enter a domain into this tool, it connects directly to the authoritative nameserver responsible for that domain and retrieves the actual records stored there. This means the results show live data, not cached information. Changes you make to your DNS records typically appear in a DNS lookup within minutes, depending on your DNS provider's setup and how DNS resolvers around the world are caching the old data.

How DNS Lookup Works

DNS lookup is a multi-step process that happens invisibly every time you navigate the web. Understanding these steps helps you troubleshoot DNS problems and know what to expect when you change DNS records.

1. 1You enter a domain name (or URL) into this tool and click lookup. The tool sends a query to a DNS resolver.
2. 2The DNS resolver checks its local cache to see if it already has the answer. If found, it returns the result immediately. If not, it proceeds to the next step.
3. 3The resolver contacts a root nameserver, which is one of 13 servers that form the foundation of the entire DNS system. The root nameserver doesn't have the answer, but it directs the resolver to the appropriate TLD nameserver.
4. 4The TLD (top-level domain) nameserver—which handles all .com, .org, .net or country-specific domains—receives the query and responds with the address of the authoritative nameserver for the domain you're looking up.
5. 5The resolver now contacts the authoritative nameserver, which is the server that actually holds the DNS records for the domain. This server returns all the records stored for that domain: A records, MX records, TXT records, and so on.
6. 6The resolver caches this response (according to the TTL value set on each record) and returns the results to your browser or tool. The entire process typically completes in milliseconds.

This tool skips most of those steps and queries the authoritative nameserver directly, which is why results appear instantly. However, the underlying process is the same. Each record returned includes a TTL (Time To Live) value measured in seconds. This TTL tells DNS resolvers and caching servers how long they should store the record before requesting a fresh copy from the authoritative server. A TTL of 3600 means the record can be cached for 1 hour; a TTL of 300 means only 5 minutes. When you change DNS records, the old TTL expires before resolvers stop using the cached old data, which is why DNS propagation takes time.

DNS Record Types Explained

DNS records are instructions stored on authoritative nameservers that tell the internet how to handle requests for a domain. Different record types serve different purposes. This tool displays six core record types, each essential for different aspects of how your domain functions.

The A record is the most fundamental: it connects your domain name to the IP address of your web server. Without it, browsers cannot reach your website. AAAA records serve the same purpose for IPv6, the newer internet protocol. Many modern networks now support IPv6, so having both A and AAAA records is a best practice for redundancy.

MX records are critical for email. They specify which mail servers should receive email sent to your domain and in what order (priority values determine which server is tried first). If your MX records are misconfigured, emails to your domain will bounce or go to the wrong server. TXT records are flexible: they store text data and are commonly used for email authentication. SPF (Sender Policy Framework) records tell receiving mail servers which servers are authorized to send email for your domain. DKIM records provide cryptographic proof that an email came from you. DMARC records define the policy for handling emails that fail SPF or DKIM checks.

NS records point to the authoritative nameservers themselves—the servers that hold all your domain's DNS records. SOA records contain administrative metadata about the zone, including the serial number (used to sync DNS records across multiple nameservers) and the email address of the domain administrator. When you change your domain's nameservers—for example, moving from your registrar's nameservers to a third-party DNS provider—you're updating the NS records at your domain registrar.

Common DNS Lookup Use Cases

DNS lookup is a troubleshooting and verification tool used by website owners, IT professionals, and system administrators. Here are the most common reasons to run a DNS lookup:

• Verifying website hosting: Confirm that your domain's A record points to the correct web server IP address. If your site is down or redirecting to the wrong place, the A record may be misconfigured.
• Checking email configuration: Look at MX records to verify that email for your domain is being routed to the correct mail servers. A common cause of missing emails is an MX record pointing to a server that no longer handles mail for your domain.
• Monitoring DNS propagation: After changing your nameservers or updating DNS records, use lookups to confirm the changes have propagated globally. New records may appear at some nameservers before others.
• Validating email authentication: Check SPF, DKIM, and DMARC records to ensure they're correctly configured. Email clients and servers check these records to verify email authenticity.
• Identifying domain owner information: SOA and NS records can reveal which nameserver provider hosts a domain's records and who administers it.
• Troubleshooting domain connectivity issues: If a domain is unreachable or email bounces, a DNS lookup helps pinpoint whether the problem is with DNS records or elsewhere.
• Security audits: Check what DNS records are publicly visible for a domain to identify potential security misconfigurations or unexpected entries.

Best Practices for DNS Lookup and Management

Understanding DNS records is one thing; managing them effectively is another. Follow these practices to avoid common DNS problems:

• Understand TTL values: Before making DNS changes, check the current TTL. If it's high (like 86400 seconds / 24 hours), lower it to 300 seconds before making changes. This lets new records propagate faster. After confirming the change worked, you can raise it again to reduce DNS queries.
• Document your records: Keep a record of what each DNS entry does and why it exists. This is invaluable when troubleshooting or migrating to a new nameserver.
• Monitor for unexpected changes: Use DNS lookup regularly to verify your records haven't been altered unexpectedly. Unauthorized DNS changes can redirect your domain to malicious sites or cause email to be rerouted.
• Check both A and AAAA records: Verify you have both IPv4 (A) and IPv6 (AAAA) records for modern web support. However, not all registrars or providers support AAAA records.
• Verify MX record priority: If you have multiple mail servers, ensure the MX records have the correct priority numbers. Lower numbers are tried first, so your primary mail server should have the lowest number.
• Test after changes: After updating DNS records, immediately run a lookup to verify the change. However, remember that global propagation takes time; your local DNS resolver may cache the old data for up to the TTL duration.

Reverse DNS Lookup and PTR Records

While this tool focuses on forward DNS lookups, reverse DNS lookup is worth understanding. A reverse DNS lookup takes an IP address and returns the domain name (or hostname) associated with it. This is the opposite of a standard lookup.

Reverse DNS is handled by PTR (Pointer) records. These records are stored in a special reverse DNS zone managed by the IP address owner—typically the ISP or hosting provider. Reverse DNS is commonly used by email servers to verify that the server sending an email is legitimate. If a mail server's IP address doesn't have a PTR record, or the PTR record doesn't match the server's hostname, spam filters may reject the email. Website hosting companies often configure PTR records for their IP ranges to help customers' emails reach inboxes.

To set up a PTR record, you typically contact your hosting provider or ISP—you can't set it directly on your domain's nameserver. This is one of the reasons why mail server configuration is complex: email authentication relies on multiple DNS record types (A, MX, SPF, DKIM, DMARC) plus PTR records that live outside your domain's nameserver.

DNS Lookup vs. Command-Line Tools

If you have access to a computer terminal, you can perform DNS lookups using command-line tools like dig, nslookup, or host. These tools are faster for people who are comfortable with terminal commands and give you granular control over which nameserver you query.

This web-based DNS lookup tool offers the same core functionality with a simpler interface. You don't need to remember command syntax or install software. Results are formatted clearly in a table, making it easy to read all of a domain's records at once. Web-based tools are ideal for quick lookups, sharing results with non-technical team members, and avoiding the learning curve of command-line tools.

Resources

Understanding DNS thoroughly helps you troubleshoot problems and configure your domain correctly. These resources provide authoritative information about DNS standards, tools, and best practices.

• RFC 1035 — The foundational specification for DNS, published by IANA. Defines how DNS works, the format of DNS messages, and all standard record types.
• ICANN DNS resources — Educational materials about how DNS works, how to manage your domain's nameservers, and general domain registry information.
• Email authentication standards — SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), and DMARC (Domain-based Message Authentication, Reporting and Conformance) are each documented in their own RFC and by email service providers.
• DNS provider documentation — Most domain registrars and DNS providers publish guides for updating records, understanding TTL, managing nameservers, and troubleshooting propagation in their control panels.
• Command-line DNS tools — The dig, nslookup, and host tools come with documentation (man pages) explaining query options, output formats, and troubleshooting techniques.

Frequently asked questions