Free Online DNS Lookup Tool
Perform live DNS queries across authoritative public resolvers with automatic failover, latency metrics, and complete zone inspection.
Domain DNS Query Console
Resolver: Cloudflare DoH (1.1.1.1)1. The Architecture of the Domain Name System (DNS)
The Domain Name System functions as the decentralized directory of the global internet. Because network routing protocols operate exclusively using numeric IP addresses (such as IPv4 192.0.2.1 or IPv6 2001:db8::1), computers cannot connect directly via domain names. DNS resolvers translate human-readable names into machine addresses.
Querying DNS records directly is essential when verifying domain ownership, setting up transactional email systems, diagnosing website outages, or configuring content delivery networks (CDNs).
2. Standard DNS Record Types Reference
| Record | Designation | Primary Function | Sample Syntax |
|---|---|---|---|
| A | Address Record | Maps a hostname to an IPv4 address | 192.0.2.45 |
| AAAA | IPv6 Address | Maps a hostname to a 128-bit IPv6 address | 2001:db8::68 |
| MX | Mail Exchange | Routes inbound email to designated mail servers | 10 mail.example.com |
| TXT | Text Information | Holds authentication records (SPF, DKIM, DMARC) | v=spf1 include:_spf.google.com ~all |
| CNAME | Canonical Name | Aliases one domain name to another domain | app.example.com → cname.service.com |
| NS | Name Server | Identifies authoritative DNS servers for the zone | ns1.cloudflare.com |
| SOA | Start of Authority | Contains zone parameters, serials, and contact email | ns1.domain.com hostmaster.domain.com ... |
3. Understanding Time to Live (TTL) & DNS Propagation
Every DNS record contains a Time to Live (TTL) value expressed in seconds. The TTL dictates how long intermediate caching resolvers (such as local ISPs and enterprise routers) can store and serve the answer before requesting a fresh copy from the authoritative nameservers.
- Low TTL (60 – 300 seconds): Ideal during server migrations and IP reassignments to ensure fast global updates.
- High TTL (86400 seconds / 24 hours): Reduces resolver query volume and DNS latency for stable production infrastructure.
4. Client-Side Privacy & DoH Architecture
This utility uses encrypted DNS-over-HTTPS (DoH) queries sent directly from your browser to public resolvers (Cloudflare and Google). Your search history, queried hostnames, and internal infrastructure investigations are never stored, logged, or tracked on MicroToolStack servers.
5. Frequently Asked Questions
Why can't I set a CNAME record on my root apex domain?
Under RFC 1912 guidelines, a CNAME record cannot coexist with any other record type for the same name. Because root domains (like example.com) must possess SOA and NS records, placing a CNAME at the apex violates DNS specifications. Use A records or DNS providers supporting CNAME flattening (such as Cloudflare or Route 53 ALIAS).
What does MX priority indicate?
The priority number in an MX record specifies delivery preference. Sending mail transfer agents attempt delivery to the server with the lowest preference number first (e.g., preference 10 is attempted before preference 20). Higher numbers serve as secondary backup mail servers.
Why do my newly updated DNS records still show old values?
Your local operating system, web browser, and ISP maintain DNS caches until the previous record's TTL expires. To view live authoritative changes immediately, flush your local DNS cache via terminal (ipconfig /flushdns or sudo dscacheutil -flushcache) or query with this online tool.