What Is A Record?

At a glance

After resolving an A record, a browser attempts to connect to its IPv4 address. With a CDN, this is usually an edge address rather than the origin.

Connecting a name to IPv4

An A record maps a name to a 32-bit IPv4 address, a common entry point for websites and Internet services. One name may return several addresses for load sharing, geographic routing or redundancy. Resolvers and clients select addresses according to the response, cache and connection policy.

An A record declares an address, not a guaranteed website, port or protocol. Browsers still connect to ports such as 80 or 443 and complete TLS and HTTP exchanges before page availability is established.

Origins, cloud hosts and CDN addresses

• An origin address may belong to a cloud provider or an organization's ASN. Ownership gives hosting clues, not the company's registered location.
• CDNs and Anycast networks may return identical or different edge addresses across regions. Public IPs often identify entry points rather than origins.
• DNS balancing can vary responses by location, health or weight. One lookup reflects a particular time and resolver location.
• Private, reserved or loopback addresses on public names are unusual for Internet access, but split DNS and internal-network uses need consideration.

Migrating addresses and diagnosing failures

Before migration, lower TTL, prepare the new server's ports, certificate and content, then change the A record. Keep the old service available while previous caches expire, and restore a suitable routine TTL afterward.

For intermittent failures, compare several resolvers and test every returned address for connectivity, TLS, Host handling and application response. Testing only one address can miss a failing node. Browsing by IP can also mislead because virtual hosting and certificates depend on the hostname.

Practical use and interpretation

Record values and TTL are directly observable. ASN, reverse names and response signals may identify a cloud or CDN provider. Shared hosting does not establish server ownership or business relationships with other sites on the IP.

Distinguish an absent record from a failed lookup. A domain with only AAAA may be IPv6-only; incomplete DNS results or network failures leave IPv4 support unknown.

Points to consider

The record shows a public destination, but IP ownership alone does not establish the website operator or physical location.

Frequently asked questions

Can one domain have several A records?

Yes, for load sharing or redundancy. DNS alone does not guarantee healthy nodes; routing services and health checks are often needed.

Does an A record reveal the website's real location?

Usually it reveals only a registered or estimated network-node location. CDNs, proxies and clouds separate it from company, team, origin and data-storage locations.

Why do users still reach the old server after an update?

Clients or recursive resolvers may retain the old TTL cache. Browsers, operating systems and applications may also retain connections or cached pages.