An A record maps a name to an IPv4 address. It is the record behind almost every website: when a browser asks for example.com, the A record is the answer that says which server to connect to.
| Type number | 1 |
| Holds | One IPv4 address per record |
| At the zone apex | Yes |
| Defined in | RFC 1035 §3.4.1 |
Look up the A records of any name
One question to DNS, answered as it is. You can change the record type too.
What it does
A name can have several A records; resolvers return them all and clients pick one, which spreads load and gives a fallback. Each record has its own TTL — how long resolvers may cache the answer before asking again.
A records work at the apex (example.com itself), unlike CNAME. IPv6 addresses go in AAAA records, which sit alongside the A records for the same name.
How it is written
| Field | Meaning |
|---|---|
| Name | The host, e.g. www or @ for the domain itself |
| TTL | Seconds a resolver may cache it |
| Value | An IPv4 address |
Examples
example.com. 3600 IN A 203.0.113.10
The domain itself points at one server, cached for an hour.
www.example.com. 300 IN A 203.0.113.10
www.example.com. 300 IN A 203.0.113.11
Two servers for www, with a five-minute TTL.
Common mistakes
- Leaving a long TTL in place before moving servers, so the old address lingers in caches for hours.
- An A record and a CNAME on the same name — a CNAME cannot share its name with anything else.
- A records left pointing at a server you no longer control, which someone else can take over.
What we recommend
Lower the TTL (to 300) a day before a planned move, then raise it again afterwards. Remove records for servers you have given up.
Watch a changed A record reach resolvers worldwide →
Questions
How long does an A record change take?
As long as the old record’s TTL: resolvers that cached it keep the old answer until it expires. With a TTL of 3600 that is up to an hour.
Sources
Checked on 25 September 2026 against these official sources:
- RFC 1035: Domain names — rfc-editor.org