An A record is a DNS record that translates a domain or hostname into a specific IPv4 address. This is what allows the internet to determine which server it should connect to when someone opens a website, an app or another service available under a specific name. So if a domain leads to a server over IPv4, the A record is what tells DNS which IP address belongs to it.

At first glance, an A record can seem like a basic technical detail that only comes up when hosting is being configured.

In reality, it is one of the most important DNS records of all. As soon as a domain or subdomain points to a specific server, the A record is very often the reason why.

What an A record actually does in practice

When a user enters a domain into the browser, the device does not automatically know which IP address it should connect to.

First, the name has to be translated into a specific numeric network destination. That is exactly the role of the A record. If the domain or hostname is available over IPv4, the A record returns the matching IPv4 address, for example 203.0.113.10.

This means the A record is not the website itself and not the server itself. It is DNS information that says which IPv4 address belongs to that name.

Why it is called an A record

The letter “A” stands for Address.

It is one of the oldest and most fundamental DNS record types. That is exactly why it appears so often – it solves one of the most basic DNS tasks possible: translating a name into the address of a server.

In practice, the important thing is that an A record does not deal with aliases, email routing or other special DNS functions. Its role is very direct – to say which IPv4 address belongs to a given name.

What an A record looks like

An A record contains two main pieces of information:

• the domain or hostname,
• the IPv4 address that name should point to.

In practice, this means that a hostname such as www.example.com may have an A record with the value 203.0.113.10. When someone opens that name, DNS returns that IP address and the browser connects to the correct server.

What is the difference between an A record and an AAAA record?

An A record and an AAAA record solve a very similar problem, but for different address families.

• A record maps a name to an IPv4 address.
• AAAA record maps a name to an IPv6 address.

So both records do similar work, but each one is used for a different version of the Internet Protocol. In practice, one domain can have both at the same time. That is common when a service should be reachable over both IPv4 and IPv6.

Where A records are used most often

An A record is used anywhere a domain or subdomain should point directly to a specific IPv4 address of a server.

Typical examples include:

• the main website,
• subdomains such as www, blog or app,
• application servers,
• internal or dedicated services accessible through a specific hostname.

That is why A records are so common when setting up hosting, moving a website or pointing subdomains to particular services.

Why a domain can have more than one A record

A domain or hostname does not have to have only one A record.

In some situations, it can have multiple IPv4 addresses at the same time. This is used, for example, for traffic distribution, higher availability or redundancy. DNS can then return multiple answers and the client connects to one of them depending on its own behaviour and network conditions.

So multiple A records are not necessarily a mistake. On the contrary, they may be part of a fully intentional and technically correct setup.

An A record is not the same thing as a CNAME

This distinction is important.

An A record points directly to an IPv4 address. CNAME, by contrast, does not point directly to an IP address at all. It creates an alias from one name to another name. So if you need a name to point directly to a specific IPv4 address, the correct choice is an A record. If you want one name to inherit its destination from another hostname, the correct choice is CNAME.

That is why these two record types should never be treated as interchangeable. They are both important, but they solve technically different tasks.

How an A record relates to a hostname

An A record is always tied to a specific name – in other words, to a domain or hostname.

That means it does not belong to “the server in general”, but to the specific name under which that server or service should be reachable. One hostname can have one A record, while another hostname can have a different one. This is exactly how DNS distinguishes which service leads to which technical destination.

How an A record relates to hosting

When hosting changes, the A record is very often one of the main things that changes with it.

If you move a website to a new server, you usually receive a new IPv4 address that the domain should point to. That is the address that needs to be written into the A record. If the domain still points to the old IP address, it will continue leading users to the previous server even after the migration.

That is why the A record is one of the first things checked when a website is moved, hosting is changed or old content is still showing after a migration.

Why an A record change does not show up immediately

Like other DNS changes, an A record change does not become visible across the whole internet immediately.

The reason is caching and the TTL value. DNS resolvers keep older answers in memory for some time before they fetch the new version. That means some users may still see the old server for a while even though the A record has already been updated.

That is why A record changes normally come with some propagation time.

What happens if the A record is missing or wrong?

If a domain or hostname needs to be reachable over IPv4 and the A record is missing, DNS will not be able to return the correct IPv4 address. The result may be an unavailable website or another unavailable service.

If the A record is configured incorrectly, the domain may point to the wrong server. This often happens during hosting migrations, manual DNS edits or simple IP-address typing mistakes.

So the practical rule is straightforward: if the domain should lead to a specific server over IPv4, the A record must be correct and current.

Why this term is worth understanding even outside technical roles

The A record is one of those terms that looks technical at first, but in reality it sits behind many everyday situations that people outside IT still have to deal with.

As soon as a website is moved to new hosting, a new subdomain is created or a domain starts pointing somewhere it should not, the A record is often part of the explanation. Once you understand what this record does, it becomes much easier to see why the domain name alone is not enough and why the internet still needs a specific IP address to reach the right server.

That is why the A record matters even outside technical professions. It is one of the simplest but most important examples of how DNS turns a human-readable name into a real network destination.

Related terms

• DNS – the A record is one of the most basic DNS record types, and its role only makes full sense in the wider context of DNS.
• IP address – the A record translates the name into a specific IPv4 address.
• Hostname – the A record is tied to a specific hostname or domain and defines which IPv4 address belongs to it.
• AAAA record – the direct counterpart of the A record for IPv6 and the clearest comparison for understanding the difference between the two address families.
• Nameservers – authoritative nameservers are where A records are stored and from where the internet looks them up.
• CNAME – an important related concept, because unlike an A record, CNAME does not point directly to an IP address, but to another hostname.