An AAAA record (pronounced "quad-A") maps a human-readable domain name to an IPv6 address (e.g., 2001:0db8:85a3:0000:0000:8a2e:0370:7334). It serves the exact same purpose as an A Record, but is designed for the modern 128-bit IPv6 protocol instead of the older 32-bit IPv4 protocol.
Did you recently enable IPv6 on your server or CDN? Check if your changes have propagated globally.
Because the internet is still transitioning from IPv4 to IPv6, most modern websites run a dual-stack configuration. This means a domain will have both an A record and an AAAA record. When a user visits your site, their browser will usually try the IPv6 connection first. If it fails or is too slow, a clever algorithm called "Happy Eyeballs" ensures the browser instantly falls back to the IPv4 address, preventing a noticeable delay for the user.
No. You should only add an AAAA record if your web server, load balancer, or CDN actively supports and listens for IPv6 traffic. If you publish an AAAA record pointing to a server that only handles IPv4, users on IPv6 networks will experience slow load times or connection timeouts.
Eventually, yes, but for the foreseeable future, they operate in parallel. You cannot replace your A record with an AAAA record yet, because users on IPv4-only networks (which is still a massive portion of the internet) would not be able to reach your website.
If you recently added or changed an AAAA record, this is a standard DNS propagation issue. Resolvers cache DNS answers based on the Time to Live (TTL). You must wait for the TTL to expire globally before all resolvers show the new IPv6 address.