DNS lookup
Enter a domain, e.g. example.com
How does DNS record lookup work?
Enter a domain name and choose a record type (A, AAAA, CNAME, MX, NS, TXT, or SOA) to query public DNS zone records via DNS-over-HTTPS. This tool queries authoritative public domain records rather than your local network resolver.
Core DNS Record Types Explained
The Domain Name System (DNS) translates human-readable hostnames into network destination addresses. An A record maps a hostname to a 32-bit IPv4 address, while an AAAA record maps to a 128-bit IPv6 address. CNAME records alias one domain name to another, MX records designate priority-weighted mail exchange servers, and TXT records hold verifiable domain configuration text.
DNS-over-HTTPS (DoH) and Resolver Privacy
Legacy DNS queries transmit unencrypted over UDP port 53, exposing domain lookups to eavesdropping, packet sniffing, and ISP manipulation. MyIPGo resolves queries using DNS-over-HTTPS (RFC 8484), wrapping lookups in end-to-end TLS encryption to guarantee data integrity and protect user privacy from upstream network observers.
Understanding DNS Propagation and TTL
Every DNS resource record includes a Time-To-Live (TTL) field specifying how long recursive resolvers are permitted to cache the answer. When changing nameservers or updating IP records, worldwide propagation is governed by these TTL expiration windows across global recursive resolvers.
Essential Email Authentication Records (MX, SPF, DKIM, DMARC)
Reliable email delivery depends on properly configured DNS records. MX records direct incoming mail to the right mail servers by priority, while TXT records publish Sender Policy Framework (SPF) allowlists, DKIM public keys, and DMARC enforcement policies. Checking TXT and MX records side by side helps diagnose bounced emails and spoofing warnings.
Troubleshooting Common DNS Failures (NXDOMAIN & SERVFAIL)
A DNS status of 0 (NOERROR) confirms the domain exists, even if a specific record type returns empty. Status 3 (NXDOMAIN) indicates the queried domain name does not exist in the authoritative zone, while Status 2 (SERVFAIL) points to broken DNSSEC signatures, unreachable authoritative nameservers, or misconfigured delegation.
Frequently Asked Questions
- What is the difference between authoritative and recursive DNS?
- Authoritative nameservers maintain the official source of truth for a domain zone. Recursive resolvers query authoritative servers on behalf of client devices and cache the results.
- Why are my recent DNS updates not showing immediately?
- If an existing record had a 24-hour TTL (86400 seconds), global DNS caches may serve the cached response until that timer expires.
- How do TXT records protect against email spoofing?
- Domain administrators publish SPF (Sender Policy Framework) and DMARC policies in TXT records, allowing recipient mail servers to verify whether sending servers are authorized.
- When should I lower my DNS TTL before a server migration?
- Lower the TTL to 60–300 seconds at least 24 hours before migrating servers so recursive resolvers expire stale IP addresses quickly during cutover.
- Can a domain have both CNAME and MX records at the apex?
- No. According to RFC 1912, a CNAME record cannot coexist with other record types at the zone apex (root domain); use A/AAAA or provider ALIAS flattening instead.
Looking for the hostname of an IP address? Try Reverse DNS.