An A record, or Address record, is a DNS record that points a domain name or subdomain to an IPv4 address. It is one of the most common DNS records used in website and service configuration. When someone visits a domain in a web browser, the A record helps direct that request to the correct server.
For Apexhost customers, A records are commonly used when connecting a domain or subdomain to a website hosting service, application server, firewall, or another internet-accessible service that uses an IPv4 address. Understanding how A records work can help you make DNS changes more confidently and reduce the risk of website or service interruptions.
What an A record does
DNS, or Domain Name System, acts like the internet’s address book. People usually remember domain names such as example.com, but computers connect to services using IP addresses. An A record links the readable domain name to the correct IPv4 address.
For example, if www.example.com has an A record that points to 203.0.113.10, a user who visits that address can be directed to the server using that IP address.
An A record is used for IPv4 only. If a service uses IPv6, the equivalent DNS record type is an AAAA record.
In simple terms, an A record tells the internet which IPv4 address a domain name should use.
When you would use an A record
A records are used in a wide range of common DNS scenarios, including:
* Pointing a root domain such as example.com to a web server
* Pointing a subdomain such as www.example.com or shop.example.com to a specific server
* Directing traffic to a hosted application, remote service or public-facing device
* Moving a website from one server to another by updating the destination IPv4 address
* Connecting a domain to external website platforms that require an IP-based destination
Before changing an A record, make sure you know which DNS service is authoritative for the domain. Updating DNS in the wrong control panel will not affect live traffic.
How A records are structured
An A record usually contains the following parts:
* Name / Host — the domain or subdomain being pointed, such as @, www or app
* Type — A
* Value / Points to / Address — the destination IPv4 address, such as 203.0.113.10
* TTL — Time To Live, which controls how long resolvers may cache the record before checking again
The exact labels may vary depending on the DNS platform, but the purpose is the same.
Common examples include:
* @ → 203.0.113.10
* www → 203.0.113.10
* app → 198.51.100.25
In many DNS editors, @ represents the root domain, also called the apex domain.
Before you begin
Before adding or changing an A record, make sure you have:
* Access to the correct DNS management portal for the domain
* Permission to update the domain’s DNS records
* The correct IPv4 address provided by your hosting, server, website platform or network administrator
* A copy of the existing DNS settings in case you need to revert the change
* An understanding of whether the change applies to the root domain, a subdomain, or both
DNS changes can affect website availability, email-related services, remote access tools and other connected systems. If you are unsure which record should be changed, review the existing configuration carefully before saving any updates.
How to add or update an A record
1. Log in to the DNS management portal or control panel that hosts the domain’s DNS zone.
2. Open the DNS management area for the domain you want to update.
3. Review the existing DNS records to identify whether an A record already exists for the host name you want to use.
4. If an A record already exists for that host name, edit the existing record rather than creating a duplicate unless your provider specifically requires multiple A records.
5. Enter the host name, such as @ for the root domain or www for a common web subdomain.
6. Select A as the record type.
7. Enter the destination IPv4 address supplied for the service.
8. Set the TTL if needed, or leave the default value if you have not been given a specific requirement.
9. Save the record.
10. Allow time for DNS caches to update before testing from all networks.
[Screenshot: DNS zone editor showing an A record for the root domain]
[Screenshot: DNS zone editor showing an A record for the www subdomain]
After the record is saved, traffic for that host name should begin resolving to the specified IPv4 address once DNS propagation and caching delays have passed.
Important notes about root domains and subdomains
Updating the root domain does not always update the www subdomain automatically, and updating www does not always update the root domain. In many DNS zones these are separate records.
For example:
* example.com may point to one IPv4 address
* www.example.com may point to the same address or a different one
If you want both addresses to load the same website, make sure the relevant DNS records are configured accordingly.
TTL and DNS propagation
TTL stands for Time To Live. It tells DNS resolvers how long they can cache a record before requesting a fresh copy. A shorter TTL may allow changes to be seen sooner by some resolvers, while a longer TTL may reduce lookup frequency.
Even after you save a new A record, not every user will see the change immediately. DNS propagation is the general term used to describe the time it takes for cached results across different networks and resolvers to refresh.
Propagation time varies depending on the previous TTL, the resolver being used, local device caching and the DNS provider. Because of this, a change may appear correct from one network while another still sees the old destination for a period of time.
Common mistakes to avoid
* Entering the wrong IP address
* Updating DNS in a control panel that is not authoritative for the domain
* Creating duplicate records for the same host without intending to use DNS round-robin behaviour
* Forgetting to update both the root domain and www where required
* Replacing an important existing record without recording the original value first
* Expecting DNS changes to apply instantly everywhere
* Confusing A records with CNAME, MX or AAAA records
Troubleshooting
The website is still loading from the old server
This usually means DNS caching is still in effect somewhere between the DNS provider, internet service provider, local network or device.
Check that the A record was saved in the correct DNS zone, confirm the entered IP address is correct, and allow additional time for propagation.
The domain does not load after changing the A record
This may happen if the new IPv4 address is incorrect, the destination server is not configured for the domain, or an essential DNS record was changed accidentally.
Review the current A record value, compare it with the intended server details, and confirm the hosting or service at the destination IP is set up to respond for that domain name.
The wrong control panel is being updated
If the domain uses external nameservers or another DNS host, changes made in a local hosting panel may not affect live DNS.
Check which nameservers are active for the domain and confirm where the authoritative DNS zone is managed before making further changes.
I need to point a domain to a hostname, not an IP address
If the destination is another hostname rather than a direct IPv4 address, you may need a CNAME record instead of an A record. The correct record type depends on the service you are connecting.
Frequently asked questions
What is the difference between an A record and an AAAA record?
An A record points to an IPv4 address. An AAAA record points to an IPv6 address.
Can I have more than one A record for the same host name?
Yes. Some services use multiple A records for redundancy or load distribution. However, you should only do this when you understand the intended behaviour and the service supports it.
Should I use an A record or a CNAME record for www?
Either may be used depending on the DNS design and hosting requirement. An A record points directly to an IPv4 address. A CNAME points one hostname to another hostname.
Does changing an A record affect email?
Not directly in most cases, because email routing usually depends on MX records. However, related services may still be affected if the same host name is used elsewhere or if other connected DNS records are changed at the same time.
Related articles
* DNS Records (DNS)
* Change DNS records
* How to create DNS records (SRV etc) for Office 365
* Welcome to Apexhost (Getting Started)
* How to Contact Apexhost Support
Need more help?
If you require further assistance, please contact Apexhost Support at support@apexhost.com.au.
