The A (address) record maps a name to one IPv4 address. It is the record a browser needs before it can open a connection to an IPv4 server.
google.com. 9 IN A 173.194.73.100 google.com. 9 IN A 173.194.73.101 google.com. 9 IN A 173.194.73.102 google.com. 9 IN A 173.194.73.113 google.com. 9 IN A 173.194.73.138 google.com. 9 IN A 173.194.73.139
github.com. 25 IN A 140.82.121.4
wikipedia.org. 98 IN A 185.15.59.224
cloudflare.com. 149 IN A 104.16.132.229 cloudflare.com. 149 IN A 104.16.133.229
An A record holds exactly one 32-bit IPv4 address. A name can have several A records; together they form an RRset, and resolvers return all of them. Clients usually try them in the order received, and many authoritative servers rotate that order, which gives simple round-robin load spreading.
A records can sit at the zone apex (example.com) and on any subdomain, and can coexist with MX, TXT, CAA and other data at the same name. That is the main practical difference from CNAME.
www.example.com. 3600 IN A 192.0.2.10
; owner TTL class type address
Wire format: RDATA is 4 octets: the address in network byte order. RDLENGTH is always 4.
| Field | Meaning |
|---|---|
| Owner | The name being resolved. An unqualified name in a zone file is relative to $ORIGIN. |
| TTL | Seconds a resolver may cache the answer. 300 to 3600 is typical; lower it a day before a planned IP change. |
| Address | Dotted-quad IPv4 address. No port, no CIDR prefix, no hostname. |
10.x, 192.168.x) copied from an internal network. Public resolvers return it and nobody outside can connect.