AAAA Record Lookup returns the IPv6 address for a domain. It does the same job as an A record but for 128-bit IPv6 addresses, written as eight groups of hexadecimal digits such as 2606:2800:220:1:248:1893:25c8:1946. The name comes from the size: an IPv6 address is four times the length of an IPv4 address, so four times the A. A domain that only has an A record is reachable over IPv4 only, which is still fine for most visitors but excludes IPv6-only networks, which are increasingly common on mobile carriers. Publishing both an A and an AAAA record makes a host dual-stack, and clients then pick between them using Happy Eyeballs, racing both connections and keeping whichever answers first. That behaviour is why a broken AAAA record is worse than no AAAA record at all: if the address is published but unreachable, some clients still pay a connection timeout before falling back. Check the AAAA record alongside A Record Lookup whenever you enable IPv6 on a host.
DNS resolution happens in multiple stages. When you type a domain name, your browser first checks its own cache, then the OS resolver cache, then queries your configured DNS resolver (usually your ISP or a public resolver like 8.8.8.8 or 1.1.1.1). If none have the record cached, the resolver performs a recursive query: it asks the root name servers for the TLD servers (.com, .net, etc.), then asks the TLD servers for the authoritative name servers of the specific domain, and finally asks the authoritative servers for the actual record. This entire process typically completes in under 100ms. DNS-over-HTTPS (DoH) encrypts DNS queries in HTTPS traffic, preventing ISPs and network observers from seeing which domains you query. It was standardized in RFC 8484 in 2018 and is now supported by all major browsers. Google and Cloudflare both operate free public DoH endpoints (dns.google and cloudflare-dns.com). TXT records have become a critical security mechanism: SPF (Sender Policy Framework) records specify which servers are allowed to send email for a domain, DKIM (DomainKeys Identified Mail) records provide public keys for verifying email signatures, and DMARC records tell receiving mail servers what to do when SPF or DKIM checks fail. Checking these records is the first step in diagnosing email deliverability problems.