An A record is a type of DNS (Domain Name System) record that maps a domain name to an IPv4 address. The “A” stands for “address” — it’s the most fundamental DNS record type, telling the internet’s routing infrastructure exactly where to find your website’s server. When someone types your domain into a browser, the A record is what translates that human-readable name into the numeric IP address computers use to communicate.

For website owners, A records are a routine but critical part of hosting setup. Whether you’re pointing a domain to a new hosting provider, migrating servers, or launching a new site, updating your A record is typically one of the first steps. Get it wrong, and visitors can’t reach your site. Get it right, and the process is invisible to everyone — which is exactly how it should be.

[Image: Diagram showing the DNS lookup flow: browser requests domain → DNS resolver → A record returns IP address → browser connects to server]

How A Records Work

When a visitor navigates to your website, their browser initiates a DNS lookup — a behind-the-scenes query that asks: “What IP address does this domain point to?” Here’s the sequence:

  1. The query begins — The visitor’s device contacts a DNS resolver (usually provided by their ISP or a public service like Google or Cloudflare).
  2. The resolver checks its cache — If the A record was recently looked up, it returns the cached result immediately.
  3. If not cached, it queries the authoritative nameserver — The nameserver for your domain returns the A record, which contains your server’s IP address.
  4. The browser connects — Using the IP address from the A record, the browser connects to your web server and loads your site.

Every A record includes a TTL (Time to Live) value — a number in seconds that tells DNS resolvers how long to cache that record before checking for updates. The default TTL for A records is 14,400 seconds (4 hours). Lower TTL values allow faster propagation when you make changes; higher TTL values reduce DNS lookup overhead.

A single domain can have multiple A records pointing to different IP addresses — a technique used for load balancing and redundancy on high-traffic sites.

Purpose & Benefits

1. Connects Your Domain to Your Hosting Server

The most direct use of an A record is pointing your domain to your WordPress hosting server’s IP address. Without this mapping, your domain exists as a name with no destination — visitors would get a “server not found” error. Properly configured A records are what make your domain functional.

2. Enables Reliable Site Migration

When you move your website to a new hosting provider, you update the A record to point to the new server’s IP address. DNS changes propagate across the internet based on the TTL setting — typically within 1 to 48 hours. Lowering your TTL in advance of a migration reduces the propagation window and minimizes downtime, which is why planning ahead matters.

3. Supports Load Balancing and Redundancy

High-traffic sites often configure multiple A records for the same domain, each pointing to a different server. When DNS resolvers receive multiple A records, they can distribute requests across servers — a technique called round-robin load balancing. This improves reliability: if one server goes down, traffic can route to another.

Examples

1. New Website Launch

A business purchases a domain and sets up WordPress hosting. The hosting provider assigns a server IP address (for example, 192.0.2.1). The business owner — or their web team — logs into the domain registrar’s DNS management panel and creates an A record: the root domain (@) pointing to that IP. Once the record propagates, the domain resolves to the hosting server and the site is live.

2. Hosting Migration

A company moves from shared hosting to a managed WordPress hosting plan for better performance. The new host provides a new server IP. The team reduces the old A record’s TTL to 300 seconds (5 minutes) several days before the migration, waits for that shorter TTL to propagate, then updates the A record to the new IP. Downtime during the switch-over is minimized to minutes rather than hours.

3. Subdomain Configuration

A business wants to run their store on shop.example.com while the main site lives on example.com. They create a separate A record for the shop subdomain pointing to the WooCommerce server’s IP address, while the root domain A record continues pointing to the main marketing site. Each subdomain can have its own A record targeting a different server.

Common Mistakes to Avoid

  • Forgetting to update all subdomain A records — If you only update the root domain A record during a migration, subdomains like www or shop may still point to the old server. Audit all DNS records before and after any migration.
  • Setting TTL too high before planned changes — A TTL of 86,400 seconds (24 hours) means DNS changes can take up to a full day to propagate everywhere. Before a migration or IP change, reduce TTL to 300–3,600 seconds well in advance.
  • Confusing A records with CNAME records — A records map directly to IP addresses; CNAME records map to another domain name. You cannot use a CNAME at the root domain level (it breaks email delivery) — root domains require A records.
  • Not verifying propagation — After updating an A record, use a DNS propagation checker to confirm the new record is resolving correctly before assuming the change is complete.

Best Practices

1. Lower Your TTL Before Any Planned Migration

Before changing hosting providers or server IP addresses, reduce your A record’s TTL to 300–3,600 seconds at least 24–48 hours in advance. This ensures DNS caches refresh quickly when you make the actual change, reducing potential downtime during the cutover. Return the TTL to a standard value (3,600 or 14,400) after the migration is confirmed successful.

2. Keep a Record of Your DNS Configuration

Maintain documentation of your complete DNS configuration — A records, CNAME records, MX records, and any others — including the values and where each is managed. This becomes invaluable during migrations, troubleshooting, or when a new team member needs to understand your infrastructure.

3. Use Your DNS Provider’s Management Tools

Most domain registrars and hosting providers offer a DNS management interface. For more control and faster propagation, consider moving DNS management to a dedicated DNS provider. Changes made through these interfaces take effect quickly once the TTL expires, and many offer propagation monitoring so you can track your updates in real time.

Frequently Asked Questions

What’s the difference between an A record and a CNAME record?

An A record maps a domain directly to an IP address — one lookup, direct connection. A CNAME record maps a domain to another domain name, which then requires a second lookup to resolve the IP. A records are faster and required for root domains; CNAMEs are more flexible for subdomains where the IP may change frequently.

How long does it take for an A record change to take effect?

It depends on the TTL setting of the existing record. Changes can propagate in as little as 5 minutes if the TTL is low, or up to 48 hours if it’s set to a long value. Most hosting migrations see full propagation within 4–24 hours under typical TTL settings.

Can I have multiple A records for the same domain?

Yes. Multiple A records for the same domain can point to different IP addresses — this is used for load balancing (distributing traffic across servers) and redundancy (failover if one server goes down). For most small and mid-size business sites, a single A record is sufficient.

What happens if my A record points to the wrong IP address?

Visitors will either see a “server not found” error or land on the wrong website — whichever server happens to be running at that IP address. This is why verifying DNS configuration before and after changes is so important, especially during hosting migrations.

Do I need an A record if I’m using Cloudflare or another CDN?

Typically yes, though the configuration changes. When using a CDN like Cloudflare in proxy mode, your A record points to your origin server, but Cloudflare serves as the public-facing address. The CDN handles the mapping between its own IPs and your origin — your A record still needs to exist and point to the correct origin server.

Related Glossary Terms

How CyberOptik Can Help

DNS configuration is one of those behind-the-scenes tasks that seems simple until something goes wrong. We handle A record setup, hosting migrations, and full DNS management for clients every day — making sure domains resolve correctly, propagation is planned in advance, and downtime is minimized. Learn about our hosting solutions or contact us to discuss your project.