What is an A record?
An A record maps a name to an IPv4 address. When someone opens your site, their resolver asks for the A record of the name and connects to the address it gets back.
A name can have several A records. Resolvers return all of them and clients pick one, which spreads traffic across servers.
How to read an A record
In a zone file, the record looks like this:
example.com. 300 IN A 192.0.2.10
- The name the record belongs to.
- The TTL: how many seconds resolvers may cache the answer.
- The IPv4 address.
From the command line
Look up A records without this site.
On macOS and Linux, use dig:
dig example.com A +short
On Windows, use nslookup:
nslookup -type=A example.com
To skip caches, ask one of the domain’s nameservers directly: dig @ns1.example.net example.com A. The “Its own nameservers” option on the result page does the same.
Questions and answers
Why do I see a different IP address than someone else?
Large sites answer with different addresses depending on where the question comes from, and they rotate addresses for load balancing. Choose “Its own nameservers” on the result page to see what the domain's nameservers return right now.
I changed my A record. Why does the old address still show?
Resolvers keep the old answer until its TTL runs out. Choose “Its own nameservers” on the result page to skip caches, and use the Trace tab to check that every nameserver already has the new value.
Can the root domain have a CNAME instead of an A record?
No. The bare domain already has SOA and NS records, and a CNAME cannot sit next to other records. Use A/AAAA records, or the ALIAS/ANAME feature some DNS hosts offer.