What is an A record?
An A record maps a domain name to one or more IPv4 addresses. It is the most fundamental DNS record, the one that tells browsers and clients which server to connect to for a hostname. Without a valid A record, a domain will not resolve to a website over IPv4.
How an A record connects a domain to a server
When you type a hostname, your resolver looks up its A record to find the IPv4 address to connect to. The record is a simple mapping, for example example.com to 93.184.216.34. A hostname can have several A records pointing to different IPs; resolvers hand them out in rotation, giving a basic form of load balancing. The A record's TTL controls how long resolvers cache the address before checking again, which matters when you move a site to a new server.
How to read your A record results
Each A record row shows a hostname, the IPv4 address it resolves to, and a TTL in seconds. A result like example.com A 93.184.216.34 TTL 3600 means the domain points to that IPv4 address and resolvers may cache it for one hour. If you see multiple A records for the same name, traffic is spread across those IPs. If the address does not match your hosting provider's server, your DNS still points at an old host and needs updating.
Common A record problems and how to fix them
The most common issue is an A record pointing at an old IP after a hosting move, which sends visitors to the wrong or dead server. Fix it by updating the record at your DNS provider and waiting for the TTL to expire. A missing A record on the root domain (example.com) means the site loads at www but not the bare domain. Conflicts also arise when you try to add an A record to a name that already has a CNAME, which DNS does not allow on the same hostname.