An A record in DNS is a type of DNS record that maps a domain name (like example.com) to an IPv4 address (like 192.0.2.1).

What Is an A Record in DNS?

In the Domain Name System (DNS), an A record (short for “Address record”) is the basic instruction that tells the internet “this domain lives at this IPv4 address.” When you type a website name into your browser, DNS looks up its A record to find the server’s IP so your browser knows where to connect.

Think of it like a phonebook entry: the domain is the person’s name, and the A record is the phone number (IP address) you actually dial.

Quick Scoop: Key Facts About A Records

  • They map a domain or subdomain to an IPv4 address only (e.g., 203.0.113.5).
  • They are one of the most fundamental DNS records ; almost every website uses them.
  • Without correct A records, users’ devices cannot find your website even if the site is up and running.
  • For IPv6 addresses, DNS uses AAAA records instead of A records.
  • A records are stored on authoritative DNS servers as part of a domain’s DNS zone data.

How an A Record Works (Step-by-Step)

  1. You type www.example.com into your browser.
  2. Your device asks a DNS resolver (usually your ISP or a public resolver) for the IP of www.example.com.
  3. The resolver eventually queries the authoritative DNS server for that domain.
  4. The authoritative server replies with the A record, for example: www.example.com -> 192.0.2.1.
  5. Your browser connects to 192.0.2.1 and loads the website.

This translation from name to IP happens in milliseconds but is absolutely critical every time you visit a site or use many online services.

What an A Record Looks Like

A typical A record has fields like:

  • Name (Host): example.com or www.example.com
  • Type: A
  • Value (IP address): 192.0.2.1
  • TTL (Time To Live): e.g. 3600 seconds (how long resolvers cache this answer)

In zone file syntax, a simplified A record might look like:

text

www   3600   IN   A   192.0.2.1

This says: "www.example.com is an A record pointing to 192.0.2.1, and can be cached for 3600 seconds."

Common Uses of A Records

  • Point the main domain to your web server
    • Example: example.com -> 93.184.216.34.
  • Point subdomains to servers
    • Example: blog.example.com -> 203.0.113.10.
  • Basic load balancing (Round Robin)
    • Multiple A records for the same name, each with a different IP, so requests are spread across several servers.
  • Failover scenarios
    • Change the A record to a backup server if the primary goes down (works together with monitoring/automation).

A Records vs Other DNS Records (HTML Table)

Below is an HTML table contrasting A records with a few common DNS record types:

html

<table>
  <thead>
    <tr>
      <th>Record Type</th>
      <th>What It Maps</th>
      <th>Main Purpose</th>
      <th>Example</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>A</td>
      <td>Domain → IPv4 address</td>
      <td>Make a domain reachable via IPv4</td>
      <td>example.com → 192.0.2.1</td>
    </tr>
    <tr>
      <td>AAAA</td>
      <td>Domain → IPv6 address</td>
      <td>Make a domain reachable via IPv6</td>
      <td>example.com → 2001:db8::1</td>
    </tr>
    <tr>
      <td>CNAME</td>
      <td>Domain → another domain</td>
      <td>Alias one name to another</td>
      <td>www.example.com → example.com</td>
    </tr>
    <tr>
      <td>MX</td>
      <td>Domain → mail server hostnames</td>
      <td>Route email for the domain</td>
      <td>example.com → mail.example.com</td>
    </tr>
  </tbody>
</table>

These other records often work alongside A records, since MX or CNAME targets typically need A (or AAAA) records to resolve to actual IPs.

Why A Records Matter in 2026

Even as IPv6 adoption grows, IPv4 and A records are still heavily used across the internet in 2026. Modern uptime and observability tools often highlight misconfigured A records as a top cause of partial outages, strange geo- behavior, or “works for some users only” incidents. Whenever someone migrates hosting, changes a CDN, or updates infrastructure, getting the A records right (and TTLs reasonable) is usually step one.

Mini Q&A Style “Forum” View

Q: If I only change my server’s IP, why doesn’t my website move automatically?
A: DNS A records still point to the old IP, so users keep going there until you update the record and caches expire.

Q: Can I have multiple A records for one domain?
A: Yes, and DNS resolvers will typically rotate between them (simple Round Robin), which can help spread load.

Q: Do I need an A record for email?
A: Email routing is controlled by MX records, but those MX hostnames usually rely on A (or AAAA) records to actually resolve to IPs.

TL;DR

An A record in DNS is the address record that connects a human-friendly domain name to its underlying IPv4 address so browsers and services know where to reach your site or server.

Information gathered from public forums or data available on the internet and portrayed here.