Domain DNS Lookup

Query live DNS records (A, AAAA, NS, MX, TXT) straight from Google's official Public DNS resolvers.

Published: January 15, 2026 Last Updated: July 26, 2026
🟢 Google DNS-over-HTTPS API

📊 Live DNS Records

Queried Domain-
A Records (IPv4)-
AAAA Records (IPv6)-
Nameservers (NS)-
Mail Exchange (MX)-
TXT Records (SPF/Verification)-

Deep Dive into DNS Architecture: Protocols, Specifications, and Diagnostics

The Domain Name System (DNS) serves as the primary address resolution framework for the global Internet infrastructure. By converting human-readable hostnames into network-routable IP addresses, DNS enables interconnected computer systems to route packets efficiently across disparate Autonomous Systems (AS). Modern network communications rely extensively on this hierarchical, distributed database architecture to maintain global scalability and fault tolerance.

RFC 1035 Standard and Implementation Protocols

The core specification governing DNS implementation is defined within RFC 1035 ("Domain Names - Implementation and Specification"), authored by Paul Mockapetris in 1987. RFC 1035 establishes the domain name space structure, message formats, resource record definitions, and master file syntax.

1. Domain Space Structure

RFC 1035 defines domain names as a tree-structured hierarchy. Each node in the tree represents a domain label up to 63 octets long. A fully qualified domain name (FQDN) cannot exceed 255 octets in total length, including trailing dots.

2. Wire Format and Packet Layout

DNS transactions operate using a standard 12-byte header followed by four variable-length payload sections: Question, Answer, Authority, and Additional. The DNS header contains the following field Layout:

+---------------------+---------------------+ | ID (16 bits) | Flags (16 bits) | +---------------------+---------------------+ | QDCOUNT (16 bits) | ANCOUNT (16 bits) | +---------------------+---------------------+ | NSCOUNT (16 bits) | ARCOUNT (16 bits) | +---------------------+---------------------+

The Recursive Resolution Process

When an application requests an IP address resolution for a host, a recursive resolver navigates through multiple authoritative tiers to complete the mapping. The following diagram illustrates the complete resolution cycle:

+----------+ +-------------------+ +----------------------+ | Client | --------> | Recursive Resolver| --------> | Root Server (.) | +----------+ +-------------------+ +----------------------+ ^ | | | | <------------------------------+ | | | | +----------------------+ | | ------------------> | TLD Server (.com) | | | +----------------------+ | | | | | <------------------------------+ | | | | +----------------------+ | | ------------------> | Authoritative Server | | | +----------------------+ | | | | | <------------------------------+ | v +---------------------------+ (Final Answer Return)

Command-Line Network Diagnostics (dig & nslookup)

Network engineers and systems administrators use dedicated command-line utilities to inspect authoritative response headers and debug DNS routing paths.

Using the `dig` Utility

`dig` (Domain Information Groper) is the industry-standard tool for performing DNS lookups due to its precise output formatting and raw protocol inspection capabilities.

# Perform a standard A record query dig example.com A +short # Query MX records with full output metadata dig example.com MX +noall +answer # Trace the complete recursive resolution path from root servers dig example.com +trace

Using the `nslookup` Utility

`nslookup` provides a cross-platform interface available across macOS, Linux, and Windows environments for quick interactive lookups.

# Non-interactive lookup for TXT records nslookup -type=TXT example.com # Query specific authoritative nameservers nslookup example.com 8.8.8.8

Resource Record Reference Architecture

A typical DNS zone file comprises multiple record types designed to perform specific network routing functions:

  • A Record: Maps hostnames directly to 32-bit IPv4 addresses.
  • AAAA Record: Maps hostnames to 128-bit IPv6 addresses.
  • NS Record: Delegates a DNS zone to use specific authoritative nameservers.
  • MX Record: Specifies mail handling servers alongside explicit priority values.
  • TXT Record: Hosts arbitrary human or machine-readable text payload used for SPF, DKIM, and site verification.
🏢

Published by SEOSmartLab Engineering Team

SEOSmartLab builds high-performance, developer-focused web utility tools and diagnostic platforms. Our team publishes technical documentation on domain routing, SEO infrastructure, and network protocols.

Community Comments & Discussion

Frequently Asked Questions

What records does this tool query?
It queries A, AAAA, NS, MX, and TXT records directly via Google's DoH service.
Is this lookup cached?
No, queries are fetched live in real time straight from public DNS endpoints.
Why do DNS changes take time to propagate globally?
DNS records rely on Time-To-Live (TTL) values cached by ISPs and local resolvers. Global propagation finishes once all older cached entries expire.
What is the difference between dig and nslookup?
dig is a modern CLI utility providing verbose output directly from name servers, whereas nslookup is a legacy tool that relies on host OS resolver libraries.
What role does RFC 1035 play in internet connectivity?
RFC 1035 specifies the implementation details of the Domain Name System, including message formats, record types, and resolver requirements.