What Is an A Record? A Complete Guide to DNS A Records

If you’ve ever tried to launch a website, connect a domain to a host, or set up a custom email, chances are you’ve encountered the term “A record.” But what is an A record in DNS, and why does it matter?

This guide explains everything you need to know about A records—from how they work to how to add them and how they compare to other DNS types like CNAME and TXT. Whether you’re configuring a domain or troubleshooting your DNS settings, this article will walk you through the essentials in plain English.

A DNS A record (short for “Address” record) is one of the most essential components of the Domain Name System. It links a domain name to an IPv4 address—the numerical address of the server that hosts your website or application.

For example, if your domain is example.com and your server IP address is 192.0.2.1, your A record will map the domain to that IP. So when someone types your domain into their browser, the DNS resolver checks the A record and sends them to the correct server.

Key characteristics of A records:

• Only supports IPv4 addresses (for IPv6, use an AAAA record)
• Can apply to root domains and subdomains
• Typically includes a TTL (Time To Live) value that defines how long the record is cached

Example A record:

example.com     A     192.0.2.1     3600

This DNS entry tells browsers: “To access example.com, go to IP 192.0.2.1, and cache this information for 3600 seconds (1 hour).”

The process begins when a user enters a domain name in their browser. The browser sends a query to a DNS resolver, which checks the DNS zone for that domain.

If an A record is present, the resolver retrieves the associated IPv4 address and returns it to the browser, which then connects to the appropriate web server.

In short:

Domain name → DNS resolver → A record lookup → IP address → Web server

This process is the foundation of how websites are accessed on the internet.

An IP address is a unique numerical label assigned to each device or server on the internet. The version used by A records is IPv4, which looks like this: 192.0.2.1.

This address acts like a street address, telling your browser exactly where to find the website or resource you’re requesting.

If you’re unsure of your server’s IP, you can use an IP address lookup tool to find it.

TTL (Time To Live) tells DNS resolvers how long to cache the A record before querying it again. It’s measured in seconds.

Common TTL values:

• 1800 seconds (30 minutes) for fast updates
• 3600 seconds (1 hour) for standard use
• 86400 seconds (1 day) for stable setups

Lower TTLs allow changes to propagate faster but increase DNS lookup traffic. Higher TTLs improve performance but delay updates.

A frequent point of confusion in DNS configuration is the difference between an A record and a CNAME record.

When to use each:

• Use an A record to point a domain directly to an IP address.
• Use a CNAME record to point one domain or subdomain to another (e.g., blog.example.com → pages.hostingplatform.com).

Tools like a CNAME lookup can help you check if your CNAME records are set correctly.

Understanding A records is crucial, but they’re just one part of a full DNS configuration. Here are some other DNS types to know:

• CNAME Record: Redirects traffic from one domain to another
• TXT Record: Used for verification (e.g., Google Search Console) and SPF/DKIM email authentication
• MX Record: Specifies the mail server for a domain
• AAAA Record: Points to an IPv6 address

These records are managed collectively in the DNS zone and define your domain’s behavior across services.

Basic steps to add a DNS A record:

1. Log in to your domain registrar
2. Go to the domain management view
3. Select the domain for which you want to mody A record
4. Click “Add new record” or “Edit existing record”
5. Select A as the record type
6. Enter your domain or subdomain in the “Name” field, the IP address in the Value field, and TTL
7. Save and wait for DNS propagation

Changes can take anywhere from 5 minutes to 24 hours to fully propagate across the web. A DNS propagation checker can help track when updates go live.

Note: Although Unstoppable offers onchain identity features, DNS records like A and CNAME remain DNS-native. Changes work the same as with any traditional DNS provider.

Yes, multiple A records can point a single domain to different IP addresses. This is common in:

• Load balancing: Traffic is distributed across multiple servers
• Failover setups: Backup servers take over if the primary server goes down

This technique is sometimes known as round-robin DNS mapping.

A records are the backbone of the modern internet. They connect domain names to IP addresses and ensure that traffic reaches the correct web server. Whether you’re launching a website or managing DNS at scale, understanding A records is a must.

From DNS zone management to record editing and propagation, having a handle on your A records empower you to build, troubleshoot, and optimize with confidence.

And with platforms like Unstoppable Domains offering integrated DNS and onchain capabilities, managing your domain has never been simpler.