Help & Troubleshooting
A Record
What this is
The A record maps a domain name to an IPv4 address. It is the most fundamental DNS record: when someone visits your website, their browser resolves the domain to the IPv4 address in the A record and connects there.
How to read your result
A healthy result shows one or more IPv4 addresses. Multiple addresses are normal for load-balanced sites. Verify the address actually belongs to your current hosting provider — an old address that still resolves is the most common surprise.
Common problems and how to fix them
No A record exists
How it shows up: The website is unreachable by name; browsers show "server not found" even though the server itself is running fine.
How to fix it: Add an A record at your DNS provider pointing to your web server's public IPv4 address. If the site should only run on www, add the A record on www and consider a redirect from the bare domain.
A record points to the old server after a migration
How it shows up: Some or all visitors still land on the old host; changes you deploy never show up for them.
How to fix it: Update the A record to the new IP at the DNS provider that is actually authoritative (check the NS records to confirm which one that is). Lower the TTL before future migrations so changes propagate faster.
Record updated but visitors still see the old site
How it shows up: You changed the A record but some networks keep resolving the old IP for hours.
How to fix it: This is TTL caching, not an error. Resolvers keep the old answer until the TTL expires. Wait out the previous TTL, and set a lower TTL (e.g. 300 seconds) ahead of planned changes next time.