A record lookup
A records map a hostname such as app.example.com to one or more IPv4 addresses.
Enter a root domain or subdomain—no protocol or path needed.
How A records work
When a browser or another client needs an IPv4 address, its resolver requests the hostname’s A records. Multiple answers can provide basic distribution or represent an anycast or load-balanced service.
The TTL is the number of seconds a resolver may cache an answer. Lowering a TTL before a planned change can shorten the time that old data remains cached, but only after the previous TTL has expired.
Common A record problems
- The record points to an old hosting address.
- The apex domain works but the www hostname is missing, or the reverse.
- A proxy or CDN address is expected but an origin address is exposed.
- A recently changed record is still cached under its previous TTL.
Quick answers
Frequently asked questions
Can an A record point to another domain?
No. An A record contains an IPv4 address. Use CNAME or a provider-specific alias feature when a hostname should follow another hostname.
Does a website need an A record?
It needs a usable address path, but that may be an A record, an AAAA record, a CNAME chain, or a provider-specific alias at the zone apex.