DNS configuration auditWhat it checks and how to fix it

What it checks

Resolves the domain's A, AAAA, MX and NS records and reads the A-record TTL from the authoritative nameservers. Warns when there is no A record, no IPv6 (AAAA) record, fewer than two nameservers, or an A-record TTL under 60 seconds, and fails when the domain does not exist. MX records are reported for information only.

Why it matters

Missing A records make the site unreachable, and a domain served by a single nameserver goes offline whenever that server does. Without AAAA records, IPv6-only networks, common on mobile carriers, have to reach you through translation gateways. TTLs under a minute force resolvers to re-query constantly, adding lookup latency for visitors and load on your nameservers.

How to fix it

Publish both an IPv4 and an IPv6 address for the site, delegate the zone to at least two nameservers (ideally on separate networks, as every managed DNS provider does), and keep TTLs at 300 seconds or more.

example.com.  300   IN  A     203.0.113.10
example.com.  300   IN  AAAA  2001:db8::10
example.com.  86400 IN  NS    ns1.dns-provider.net.
example.com.  86400 IN  NS    ns2.dns-provider.net.

If your server has no IPv6 address, putting the site behind a CDN such as Cloudflare (proxied records) gives it AAAA records automatically. Lower TTLs temporarily before a planned migration, then raise them again.

Check the result:

dig +short A example.com
dig +short AAAA example.com
dig +short NS example.com
dig +noall +answer A example.com @ns1.dns-provider.net