The A record is the single most important DNS record you will ever deal with — it is what actually connects your domain name to your website. If your site is not loading, or you are moving to a new host, or you are pointing a domain somewhere for the first time, the A record is almost always at the heart of it. Fortunately, it is also one of the simplest records to understand and set up.
This guide explains what an A record is, why it matters, and exactly how to create or edit one step by step. You will learn how the root domain and subdomains work, the difference between an A record and its close relatives (CNAME and AAAA), the most common use case, and how to troubleshoot when a change does not seem to take effect. No jargon, just a clear walkthrough.
Did you know?
The “A” in A record stands for “Address.” It is the DNS record that maps your domain name to the numeric IPv4 address of the server hosting your site — the fundamental link that turns a name into a working website.
What an A record is
An A record — short for Address record — is the core DNS record that maps a domain name to an IPv4 address. It tells the internet that a name like example.com corresponds to a specific numeric address, such as 192.0.2.1, which is where the website’s server lives.
When someone types your domain, DNS looks up its A record to find the IP address of the server, and the browser then connects to that server to load your site. In other words, the A record is the bridge between the memorable name people type and the numeric address computers actually use to reach your website.
Because it points directly at an IP address, the A record is what you use whenever you need to connect your root domain to a server. It is the most direct, foundational form of “pointing” a domain, and nearly every live website has at least one.
Why the A record matters
The A record matters because without a correct one, your domain simply will not lead to your website. It is the record that makes your name resolve to your hosting server, so getting it right is the difference between a working site and a browser error.
It is also central to some of the most common tasks a domain owner performs. Launching a new site on a host, migrating to a different hosting provider, or pointing a domain you registered elsewhere at your server all come down to setting or updating the A record with the correct IP address.
Understanding the A record therefore gives you real control. When you know it maps your name to a server’s IP, you can confidently point your domain wherever you need, diagnose why a site is not loading, and make hosting changes without confusion.
Root domain vs subdomains: the host field
Every A record has a host (or name) field that determines which part of your domain it applies to. For your root domain — example.com itself — the host is usually entered as @ (or sometimes left blank or shown as the domain name), meaning “the domain at its base.”
For a subdomain, you enter the subdomain’s label. An A record with the host set to blog points blog.example.com at an IP address; one set to shop points shop.example.com. This lets different parts of your domain resolve to different servers if needed.
Many sites also want www.example.com to work. That can be handled with its own A record pointing to the same IP, or more commonly with a CNAME that aliases www to the root domain. Understanding the host field is what lets you point exactly the right name at the right place.
How to set up an A record, step by step
Creating or editing an A record follows the same pattern at almost every registrar and host. Here is the general process:
- Log in to the dashboard of whoever manages your DNS — your registrar or hosting provider.
- Open the DNS management or zone editor section for your domain.
- Add or edit a record and choose the type A.
- Set the host/name: use @ for the root domain, or a label like blog for a subdomain.
- Enter the value: the IPv4 address of your server (provided by your host).
- Set the TTL (time to live), or leave the default.
- Save the record, then wait for propagation to complete.
That is the entire process. The two fields that matter most are the host (which name you are pointing) and the value (the IP address it points to). Get those correct, save, and your domain will resolve to that server once the change propagates.
A record vs AAAA vs CNAME
It helps to see how the A record differs from its two closest relatives, because choosing the right one avoids common mistakes.
Use an A record when you have an IPv4 address to point to — the most common situation. Use AAAA when you have an IPv6 address (often set up automatically by your host). Use a CNAME when you want to alias a subdomain to another name rather than a numeric address. The A record is your default for connecting a domain to a server.
The most common use: pointing a domain to hosting
By far the most frequent reason to touch an A record is connecting your domain to your web hosting. Your host gives you a server IP address, and you create an A record with the host set to @ and the value set to that IP — instantly telling the world that your root domain lives on that server.
If you registered your domain in one place and host your site in another, this is the step that ties them together. You do not need to move your domain; you simply point its A record at your host’s IP, and visitors typing your domain will reach your site.
When you later change hosts, you repeat the process with the new server’s IP. Updating that single value redirects your domain to the new home, which is why the A record is the linchpin of both launching and migrating a website.
Need somewhere to point your A record?
Hostinger gives you a clear server IP and an easy DNS editor, so setting your A record and getting your domain live takes minutes — with a free domain included on its hosting plans to make the whole setup seamless.
Troubleshooting and propagation
If your domain does not resolve after setting an A record, the most common cause is simply propagation — the delay while the change spreads across cached DNS servers worldwide. This can take from a few minutes up to 48 hours, so a brief wait often resolves the issue on its own.
If it still does not work after propagation, check the basics: is the IP address exactly correct, with no typos? Is the host field right (@ for the root, the correct label for a subdomain)? And critically, are your domain’s nameservers pointing to the DNS provider where you made the change — because editing an A record has no effect if your nameservers point somewhere else.
A useful habit before a planned change is to lower the record’s TTL in advance, so caches expire faster and your update takes effect sooner. Otherwise, make the change once and let it settle rather than editing repeatedly, which only restarts the propagation clock.
FAQs
What is an A record?
An A (Address) record is the core DNS record that maps a domain name to an IPv4 address — for example, pointing example.com to 192.0.2.1. It is the fundamental link that connects your domain to the server hosting your website, so when someone types your domain, DNS uses the A record to find the right server and load your site.
How do I set up an A record?
Log in to your DNS provider (registrar or host), open the DNS or zone editor, add a record of type A, set the host to @ for your root domain (or a label for a subdomain), enter your server’s IPv4 address as the value, set or keep the TTL, and save. Then wait for propagation, which can take minutes to 48 hours.
What is the difference between an A record and a CNAME?
An A record points a name to a numeric IPv4 address (a server), while a CNAME points a name to another domain name (an alias) and never to an IP. Use an A record for your root domain and direct server pointing; use a CNAME for subdomains and aliases. A CNAME also cannot be used on the root domain.
What is the difference between an A record and an AAAA record?
They do the same job for different address types: an A record maps a domain to an IPv4 address, while an AAAA record maps it to an IPv6 address. A site can have both for dual-stack support. Hosts usually configure AAAA automatically, so most owners set A records and rarely need to touch AAAA directly.
Why is my A record not working?
Usually propagation — the change can take minutes to 48 hours to spread. If it still fails, check that the IP address and host field are exactly correct, and confirm your domain’s nameservers point to the DNS provider where you made the change. Editing an A record has no effect if your nameservers point somewhere else entirely.
What do I put in the host field of an A record?
Use @ (or your domain name, or blank, depending on the provider) for the root domain like example.com. For a subdomain, enter its label — blog for blog.example.com, shop for shop.example.com. The host field decides which part of your domain the record applies to, while the value field holds the IP address it points to.
The bottom line
An A record is the Address record that maps your domain to an IPv4 address, making it the fundamental link that connects your name to the server hosting your website. It is the record you set to point a domain at your hosting, to launch a new site, and to migrate to a new host — which is why understanding it gives you genuine control over where your domain leads. Setting one up is a simple, repeatable process: open your DNS editor, add an A record, set the host (@ for the root or a label for a subdomain), enter your server’s IP, and save.
When choosing between record types, reach for an A record to point a name at an IPv4 address, an AAAA record for IPv6 (usually handled by your host), and a CNAME to alias a subdomain to another name. If a change does not take effect, propagation is the usual culprit — followed by typos, the wrong host field, or nameservers pointing to a different DNS provider than the one you edited. Get the host and value right, be patient through propagation, and the A record will reliably turn your domain into a working website.
When you are ready, you can start with Hostinger and use code PROTIPS for the reader discount. An A record maps your domain to your server’s IPv4 address — the core link that makes your site load. Set it in your DNS editor (@ for root), enter the IP, save, and wait for propagation.