DNS Lookup
DNS Lookup helps you query dns records (a, aaaa, cname, txt, ns, soa), for authoritative DNS validation, resolver checks, and faster troubleshooting.
Advertisement · Anuncio
Advertisement · Anuncio
Technical Analysis & Guide
What It Does
DNS Lookup resolves domain names to IP addresses by querying DNS A (IPv4) and AAAA (IPv6) records. This is the fundamental process that allows browsers and applications to connect to websites and services.
Why It Matters
- →Website Accessibility: Must resolve correctly for your website to be reachable
- →Performance: Fast DNS resolution improves loading times
- →IPv6 Support: AAAA records ensure compatibility with modern networks
- →CDN Configuration: Multiple A records can distribute traffic across servers
How to Read Results
- A Records: IPv4 addresses (e.g., 192.0.2.1) - most common
- AAAA Records: IPv6 addresses (e.g., 2001:db8::1) - newer standard
- Multiple IPs: Indicates load balancing or redundancy
- TTL: Lower values = faster propagation of changes, but more DNS queries
Technical Background
DNS (Domain Name System) lookup is the process of resolving a human-readable domain name into a machine-readable IP address, defined in RFC 1034 and RFC 1035. The resolution process follows a hierarchical chain: the resolver first checks its local cache, then queries the recursive resolver (usually provided by the ISP or configured manually, e.g., 8.8.8.8), which in turn queries the root name servers, TLD (.com, .net) authoritative servers, and finally the domain's authoritative name servers. DNS supports multiple record types: A records map to IPv4, AAAA to IPv6, CNAME creates aliases, NS delegates authority, SOA defines zone parameters, TXT carries arbitrary data (SPF, DKIM, DMARC, domain verification), MX routes email, PTR enables reverse lookup, and SRV locates services. DNS responses include a TTL (Time to Live) value specifying how long resolvers should cache the result — lower TTLs increase load on name servers but enable faster propagation of changes. DNSSEC (RFC 4033-4035) adds cryptographic authentication to DNS responses, preventing cache poisoning attacks. Understanding A and AAAA record lookups is fundamental for diagnosing connectivity issues, verifying CDN configuration, and confirming that DNS changes have propagated correctly across global resolvers.
DNS propagation occurs when changes to DNS records are distributed across the global network of resolvers and caches. New records or changes may take minutes to 48 hours to propagate fully, depending on the old TTL value — a record with TTL 86400 (24 hours) may be cached for a full day before resolvers re-query. Tools like dig, nslookup, and online propagation checkers query multiple resolvers worldwide to verify propagation status. Common DNS issues include: stale cache causing old IP to be returned, missing A records for subdomains, CNAME loops, and wildcard record conflicts. Understanding DNS lookup mechanics is essential for web administrators, DevOps engineers, and security professionals managing domain infrastructure.
Cloud and CDN architectures create complex DNS configurations: CNAME flattening (ALIAS or ANAME records) allows CNAME-like behavior at the apex domain. Anycast routing used by CDNs like Cloudflare and Akamai means different clients may resolve the same domain to different IPs based on geographic location — this is by design for performance. Split-horizon DNS serves different answers to internal vs external queries. DNS over HTTPS (DoH, RFC 8484) and DNS over TLS (DoT, RFC 7858) encrypt DNS queries to prevent ISP surveillance and MITM interception. Understanding DNS lookup behavior helps troubleshoot issues with CDN configuration, geographic routing, and DNS-based load balancing.
Common Errors and How to Fix Them
- ProblemA CNAME was created at the zone apex (example.com CNAME myapp.hosting.net) and now MX and TXT records stop resolving.
- FixRFC 1034 section 3.6.2 forbids a CNAME next to other records, and the apex always has SOA and NS. Use plain A/AAAA records or your DNS provider's ALIAS/ANAME (CNAME flattening) feature at the apex.
- ProblemAn outdated AAAA record still points to a decommissioned IPv6 server, so users on IPv6 networks get timeouts while IPv4 users load the site fine.
- FixUpdate or delete the AAAA record whenever the server moves. Test both families explicitly with 'curl -4' and 'curl -6' after any migration.
- ProblemThe A record was changed but visitors keep reaching the old server for a full day.
- FixThe previous record carried TTL 86400. Before planned moves, lower the TTL to 300 at least one old-TTL period in advance, make the change, then raise it again once traffic has shifted.
- ProblemRecords are edited in the registrar's DNS panel, but the domain is delegated to another provider's nameservers, so nothing changes.
- FixCheck the NS records first. Only the provider listed there is authoritative; make the change in that panel or move the delegation back to the registrar.
- ProblemThe apex resolves but www.example.com returns NXDOMAIN, breaking links and certificates that include www.
- FixAdd 'www CNAME example.com.' (or an A/AAAA pair) and make sure the TLS certificate lists both names, then redirect one to the other.
- ProblemAn internal address such as 10.0.0.15 or 192.168.1.20 is published in public DNS, leaking network layout and failing for outside users.
- FixUse split-horizon DNS: serve private addresses only from internal resolvers and keep the public zone limited to routable addresses.
Frequently Asked Questions
Why do I get a different IP address than my colleague in another country?
Many sites sit behind CDNs or global load balancers that answer with the edge location closest to the resolver making the query, a technique often called GeoDNS. Round-robin pools also rotate the order of several A records. Both are normal. A mismatch only signals a problem when one of the returned addresses belongs to infrastructure you have already retired.
What is the difference between NXDOMAIN and an empty answer?
NXDOMAIN means the name itself does not exist anywhere in the zone. A NOERROR response with zero answers, sometimes called NODATA, means the name exists but has no record of the type requested, for example a hostname with an AAAA record but no A record. Distinguishing the two tells you whether to create the name or just add the missing record type.
What TTL should I use for A and AAAA records?
For stable production servers, 3600 seconds (one hour) is a sensible balance between resolver load and agility. Use 300 seconds during migrations or when a failover system needs to swap addresses quickly. Values below 60 seconds are often clamped by resolvers anyway and mostly increase query volume without making changes noticeably faster.
I changed my DNS but my browser still opens the old site. Why?
Several caches sit between you and the authoritative server: the browser, the operating system and the recursive resolver. Each holds the old answer until its TTL expires. Flush locally with 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder' on macOS or 'ipconfig /flushdns' on Windows, and compare against this tool's result to see whether the authoritative change is already live.
Does a domain need both A and AAAA records?
Only an A record is strictly required for reachability today, but publishing an AAAA record lets IPv6-only and dual-stack mobile networks connect without passing through NAT64 translation. Add the AAAA only when the server genuinely listens on that IPv6 address and the firewall permits it; a broken AAAA is worse than none because clients try it first.
Academic Documentation
Protocol context and primary references
REST API Documentation
v1.0GET /api/tools/dns-lookup
curl -X POST https://epcybertools.com/api/tools/dns-lookup \
-H "Content-Type: application/json" \
-d '{"domain":"google.com"}'
{
"success": true,
"results": [
{ "test": "Sample Check", "status": "pass", "message": "All clear" }
]
}
Usage Examples
# Full DNS record lookup
dig A example.com
# Query all record types
dig ANY example.com
# Use specific DNS server
dig @1.1.1.1 A example.com +short
# IPv6 AAAA record
dig AAAA example.com