Home / Core Health / Fix your domain's A/AAAA DNS record so it resolves correctly
Domain & DNS Health · Scan Check Guide

Fix your domain's A/AAAA DNS record so it resolves correctly

15 min Impact: high Effort: medium ✓ Scan-verified — no manual checkbox

The A (and AAAA for IPv6) record is the fundamental DNS entry that maps your domain name to the actual server IP address — this is the most basic building block of your site being reachable at all, and errors here mean total outages, not partial issues.

An A record points your domain name to an IP address. Without it, your domain doesn't resolve — no one can reach your site. This is the most fundamental DNS record.

The full picture

Correct A and AAAA DNS records represent the fundamental technical mechanism that actually allows your domain to resolve to your server at all — these records translate your human-readable domain name into the actual numeric IP address browsers and other systems need to establish a connection, making their accuracy a genuine prerequisite for your site being reachable at all.

Misconfiguration here can produce a range of failure modes depending on the specific nature of the error — from complete site unreachability if the record points to an entirely incorrect or non-existent address, to more subtle, intermittent issues if records are inconsistent or improperly configured across different query types.

The AAAA record specifically handles IPv6 addressing, distinct from the A record's IPv4 addressing — as IPv6 adoption continues growing across internet infrastructure, ensuring both record types are correctly configured, where your hosting genuinely supports both, provides broader compatibility across the full range of network configurations your visitors might be using.

This represents genuinely foundational infrastructure that every other technical and SEO check throughout this broader hardening work implicitly depends on — none of the more sophisticated optimizations discussed elsewhere matter if this fundamental resolution mechanism isn't correctly configured, making this check's verification a genuine prerequisite worth confirming before investing effort in more advanced optimization.

How to fix it

  1. 1
    Verify your A record points to your current server
    Check via DNS lookup that the IP address matches your actual current hosting provider — a leftover record from an old host is a common issue after migration.
  2. 2
    Add an AAAA record for IPv6 if your host supports it
    Increasingly relevant as IPv6 adoption grows — check if your host provides an IPv6 address to add.
  3. 3
    Confirm propagation after any change
    DNS changes can take up to 48 hours to fully propagate globally — verify from multiple locations/tools, not just your own connection.

Common mistakes

How you'll know it's done

Your A record (and AAAA, if applicable) correctly points to your current, active hosting server.

Tools that help

H.I.V.E. checks this automatically

Fix it, then re-scan — the check confirms itself. No manual checkbox, the scan is the truth.

Run this check in H.I.V.E. →