DNS Lookup
Query DNS records for a domain and review the values that browsers, mail servers, verification services, and infrastructure providers rely on. DNS lookup is useful when you are launching a site, moving hosting, configuring email, validating ownership, or investigating why users are reaching the wrong server.
DNS Lookup
Query DNS records for a domain (A, MX, TXT, NS, etc.)
Records you can verify
- A and AAAA records show where web traffic is routed for IPv4 and IPv6.
- MX records identify which mail servers receive messages for the domain.
- TXT records often hold SPF, DKIM, DMARC, and service-verification values.
- NS and CNAME records help explain delegation and alias behavior.
When DNS results differ
DNS can vary because of TTL caching, resolver choice, split-horizon networks, DNSSEC issues, or recent changes that have not propagated. If a lookup disagrees with your DNS provider, compare authoritative nameservers, propagation checks, and local resolver cache before changing production records.
DNS troubleshooting checklist
- Confirm the domain uses the nameservers you expect at the registrar.
- Check that the record type and host name match the provider instructions exactly.
- Review TTL values so you know whether old answers may still be cached.
- Use propagation and trace tools when one resolver returns a different answer.
IP, DNS & Security Tools
What Is a DNS Lookup?
A DNS Lookup is the process of translating a human-readable domain name, such as example.com, into the technical records computers need to connect to websites, mail servers, and other internet services.
The most familiar DNS lookup returns an IP address, but DNS can also provide mail routing, domain verification records, name servers, aliases, and security-related information.
Without DNS, users would need to remember IP addresses instead of domain names. DNS is what allows a browser to turn a simple name into a reachable destination.
How Does a DNS Lookup Work?
When you enter a domain into your browser, several DNS checks may happen before the website loads.
Step-by-step process
- The browser checks its local DNS cache
- The operating system checks its own resolver cache
- The request is sent to a recursive DNS resolver
- The resolver queries root DNS servers if needed
- The root server points to the correct TLD name servers
- The TLD servers point to the authoritative name servers
- The authoritative server returns the requested DNS record
- The result is cached based on its TTL value
This usually happens very quickly, but a slow or broken DNS lookup can make a website appear unavailable even when the web server itself is healthy.
Common DNS Record Types
A record
An A record maps a domain name to an IPv4 address, such as 93.184.216.34.
AAAA record
An AAAA record maps a domain name to an IPv6 address.
CNAME record
A CNAME record creates an alias from one hostname to another. It is commonly used for subdomains such as www, blog, or docs.
MX record
An MX record specifies which mail servers receive email for a domain.
NS record
An NS record identifies the authoritative name servers for a domain.
TXT record
A TXT record stores text data. Common uses include domain verification, SPF, DKIM, DMARC, and other security policies.
SOA record
An SOA record contains administrative information about a DNS zone, including serial number and timing values used by secondary name servers.
Why DNS Lookup Is Important
Website accessibility
If DNS records are missing or incorrect, users may not be able to reach the website at all.
Performance
DNS resolution is one of the first steps in loading a page. Slow DNS responses can increase perceived load time before the browser even connects to the server.
Email deliverability
MX, SPF, DKIM, and DMARC records influence whether email from your domain is accepted, rejected, or marked as spam.
Security
DNS records help verify domain ownership, support certificate issuance, and protect against spoofed email.
Troubleshooting
DNS lookup tools help identify misconfigurations, propagation delays, stale records, and resolver-specific differences.
How to Read DNS Lookup Results
When reviewing DNS results, pay attention to these fields:
| Field | What it means |
|---|---|
| Record type | The type of DNS data requested, such as A, MX, or TXT |
| Value | The returned IP address, hostname, mail server, or text value |
| TTL | How long resolvers may cache the record |
| Resolver | The DNS server that returned the answer |
| Status | Whether the lookup succeeded, failed, or returned no records |
A result with no records does not always mean the domain is broken. It may only mean that the specific record type you queried is not configured.
Common DNS Lookup Issues
DNS records are misconfigured
A common mistake is pointing the root domain to one IP address while www points somewhere else. Another is leaving old records in place after a hosting migration.
DNS propagation is still in progress
After changing DNS records, different resolvers may return different answers until caches expire. This is why one user may see the new site while another still sees the old one.
The domain expired
Expired domains may stop resolving, show registrar parking pages, or return unexpected DNS records.
Name servers are incorrect
If the domain points to the wrong authoritative name servers, your intended DNS zone may never be used.
TXT records are malformed
Email and verification records are often sensitive to small formatting mistakes. A missing quote, extra space, or duplicate SPF record can cause verification failures.
DNS Lookup vs DNS Propagation Check
A normal DNS lookup usually asks one resolver for one answer. A DNS propagation check compares results from multiple resolvers or locations.
Use a DNS lookup when you want to inspect a specific record. Use a propagation check when you want to know whether recent changes are visible across different networks.
DNS Lookup vs WHOIS Lookup
- DNS Lookup focuses on technical routing and service records
- WHOIS Lookup focuses on registration, registrar, ownership, and lifecycle details
Both tools are useful, but they answer different questions. If a website is not working, DNS tells you where traffic should go, while WHOIS can tell you whether the domain itself is registered and active.
Practical DNS Troubleshooting Checklist
When a domain is not working, check in this order:
- Confirm the domain is registered and not expired
- Check NS records to verify the authoritative name servers
- Check A and AAAA records for the root domain
- Check CNAME records for subdomains such as
www - Check MX records if email is affected
- Review TXT records for SPF, DKIM, DMARC, or verification issues
- Compare results from multiple resolvers if you recently made changes
- Wait for TTL expiration if propagation is still in progress
This workflow helps separate DNS problems from hosting, application, CDN, or browser-cache issues.
Is DNS Lookup Legal?
Yes. DNS lookup uses public DNS data and is a normal part of how the internet functions.
It is safe and legitimate for troubleshooting, website administration, security review, and educational purposes.
Limitations of DNS Lookup Tools
- Cached results may vary by resolver
- Geo-based DNS can return different answers by location
- Some private or internal records are not visible publicly
- DNSSEC or resolver behavior may affect results
- Recent changes may not appear everywhere immediately
Always test from more than one resolver or location when accuracy matters.
Conclusion
A DNS Lookup is one of the most important tools for understanding how a domain connects to websites, email, and other internet services.
By learning how to read DNS records, TTL values, and resolver results, you can troubleshoot outages faster, avoid configuration mistakes, and keep your domain infrastructure more reliable.