DNS & Domain Guides

What Is an A Record and How to Configure It

Learn what an A record does, when to use it, how it connects a domain to an IPv4 address, and how to configure it without breaking website access.

By CheckDomainHealth Editorial Team Reviewed by Dionis Ceban Updated Jun 28, 2026 7 min read Beginner

Introduction

An A record is one of the most important DNS records for a website. It tells DNS which IPv4 address should be used when someone visits a domain or subdomain.

For example, if example.com should load from a hosting server with the IP address 192.0.2.10, the domain needs an A record pointing to that IP. If the A record is missing or points to the wrong server, the website may not load, may show the wrong site, or may fail during a hosting migration.

Quick answer

Quick answer

An A record maps a domain or subdomain to an IPv4 address. It is commonly used to point a root domain like example.com or a subdomain like app.example.com to a hosting server. A records are used for IPv4 only; IPv6 addresses use AAAA records.

What is an A record?

An A record, short for Address record, connects a hostname to an IPv4 address. It is used when a domain needs to point directly to a server.

Example 
example.com → 192.0.2.10

In this example, example.com resolves to the server at 192.0.2.10. The browser can then connect to that server and request the website.

The IP address 192.0.2.10 is an example address used for documentation. Replace it with the real IP address from your hosting provider.

When should you use an A record?

Root domain

Use an A record when the main domain, such as example.com, should point to a hosting server.

Subdomain pointing to a server

Use an A record when a subdomain, such as app.example.com or panel.example.com, should point directly to a server IP.

VPS or dedicated server

Use an A record when your website or application is hosted on a VPS or dedicated server with a fixed IPv4 address.

Hosting migration

Update the A record when moving a website from one server or provider to another.

Do not change an A record during migration unless you know the new server is ready to handle the website.

A record vs CNAME

An A record points a hostname directly to an IPv4 address. A CNAME points a hostname to another hostname.

A record

  • Points to an IPv4 address
  • Used for root domains and server IPs

example.com → 192.0.2.10

CNAME

  • Points to another hostname
  • Common for www, CDN services and SaaS platforms

www.example.com → example.com

The root domain usually uses an A record or provider-specific ALIAS/ANAME record. Many DNS providers do not allow a CNAME at the root domain.

Root domain and www records

A common setup uses an A record for the root domain and either an A record or CNAME for www.

Example setup 
example.com      A      192.0.2.10
www.example.com  CNAME  example.com
Alternative setup 
example.com      A      192.0.2.10
www.example.com  A      192.0.2.10

Both setups can work. The important part is that root and www point to the intended website and your web server or hosting platform is configured to handle both versions.

Why this matters

Why this matters

A wrong A record can send visitors to the wrong server, show an old website, break a migration, or make a domain appear offline. A records are also important for SSL certificates, because the certificate must be installed on the server that actually receives the website traffic.

How to check an A record

Use the DNS Lookup tool to check the A record for your domain or subdomain.

What to compare

When checking an A record, compare these four values.

Hostname

The domain or subdomain you are checking, such as example.com or app.example.com.

Current IP address

The IPv4 address currently returned by public DNS.

Expected server IP

The IPv4 address provided by your hosting, VPS, CDN or website platform.

Active nameserver

The DNS provider currently controlling the live DNS zone.

If the current IP does not match the expected server IP, first confirm that you are editing DNS at the active nameserver provider.

Check A record now

Use DNS Lookup to confirm which IPv4 address your domain currently points to.

Run DNS Lookup →

Common A record problems

A record points to the wrong IP

High

The domain points to an old server, wrong hosting account or incorrect VPS IP.

Next step: Confirm the correct server IP and update the A record at the active DNS provider.

Root domain has no A record

High

The main domain may not resolve to a website if no A, AAAA, ALIAS or equivalent record exists.

Next step: Add the correct record based on your hosting provider’s instructions.

www works but root domain does not

Medium

The www hostname may be configured, but the root domain may be missing an A record or equivalent setup.

Next step: Check both example.com and www.example.com.

Root works but www does not

Medium

The root domain points correctly, but www may be missing or pointing elsewhere.

Next step: Add a CNAME or A record for www, depending on your provider’s recommendation.

Multiple A records are unintentional

Medium

Multiple A records can be valid, but if they point to different unrelated servers, users may reach inconsistent destinations.

Next step: Remove old or unintended A records unless you are intentionally using multiple IPs.

A record changed but site still shows old server

Low

DNS caches may still return the old IP until TTL expires.

Next step: Wait for cache expiry and check from multiple DNS resolvers.

A record points to server but website still fails

Medium

DNS may be correct, but the web server, virtual host, SSL certificate or hosting configuration may not be ready.

Next step: Check web server configuration, hosting settings and SSL.

How to configure or fix an A record

  1. Find the correct server IP

    Get the IPv4 address from your hosting provider, VPS panel, CDN provider or website platform. Do not guess the IP address.

  2. Confirm where DNS is hosted

    Check the active nameservers for the domain. Make DNS changes at the provider that controls those nameservers.

  3. Open the DNS zone

    Go to the DNS management area for the domain and find the record for the hostname you want to configure.

  4. Add or update the A record

    Set the hostname and IPv4 address.

    Type: A
Host: @
Value: 192.0.2.10
TTL: 300 or 3600

    The @ symbol usually represents the root domain, but some DNS providers use the full domain name instead.

  5. Configure www if needed

    If the website should also work on www.example.com, add a CNAME or A record for www.

    Type: CNAME
Host: www
Value: example.com
  6. Wait for DNS cache and verify

    DNS changes may appear quickly, but cached values can remain until TTL expires. Use DNS Lookup to verify the result.

  7. Check the website and SSL

    After DNS points to the correct server, confirm that the website loads and the SSL certificate is valid for the domain.

A record examples

A record example 
example.com.      300   IN   A      192.0.2.10
app.example.com.  300   IN   A      192.0.2.20
www CNAME example 
www.example.com.  300   IN   CNAME  example.com.

These are examples only. Replace hostnames and IP addresses with values from your provider.

Check commands 
dig example.com A
dig www.example.com A

What happens after changing an A record?

After an A record is changed, new DNS lookups should start returning the new IP address. However, some users may still reach the old IP until cached DNS values expire.

During a website migration, this can mean some visitors see the old server while others see the new server for a short time.

Before changing the A record, make sure the new server already has the website files, database, redirects and SSL certificate ready.

A records and SSL certificates

An A record controls which server receives traffic for the domain. The SSL certificate must be installed on that server or handled by the CDN/proxy in front of it.

If an A record points to the wrong server, users may see SSL warnings, certificate mismatch errors or the wrong website.

Frequently asked questions

Can a domain have multiple A records?

Yes. A domain can have multiple A records, usually for redundancy or load balancing. However, this should be intentional. Unrelated old IPs can cause inconsistent website behavior.

Is an A record the same as a CNAME?

No. An A record points to an IPv4 address. A CNAME points to another hostname.

Can I use a CNAME instead of an A record?

For subdomains, often yes. For the root domain, many DNS providers do not allow a normal CNAME, although some offer ALIAS or ANAME records.

How long does an A record change take?

Many changes appear within minutes, but cached DNS values can remain until the previous TTL expires.

Why does my domain still show the old website?

The old A record may still be cached, or the DNS change may have been made at the wrong provider. It is also possible that the new server is serving old content.

Does changing an A record affect email?

Usually not directly. Email delivery mainly depends on MX records and email authentication records. However, some setups use mail subdomains that may also have A records.

Should www be an A record or CNAME?

Both can work. Many setups use a CNAME for www pointing to the root domain, while others use an A record pointing to the same server IP.

Use these free tools to verify your configuration after applying changes.

DNS Lookup Domain Health Checker SSL Checker Website Status Checker WHOIS Lookup CAA Record Checker
Understanding DNS: How Domain Names Connect to Websites and Email 8 min read What Is a CNAME Record 5 min read What Is an AAAA Record 5 min read Understanding TTL: DNS Cache and Propagation Times 8 min read How to Run a Complete Domain Health Check 9 min read "Domain Not Found" DNS Errors: Causes and Fixes 8 min read
Browse all DNS & Domain guides →

Need help applying this fix?

Send us your domain, report link or issue details. CheckDomainHealth will review the request and route it to the right technical team if hands-on support is needed.

Get Help Run Domain Health Check

Was this guide helpful?

Your feedback helps us improve our guides for everyone.