Updated on:  
January 21, 2025

What is A record

An A record, also known as an Address record, is one of the most basic and essential types of DNS records. It connects a domain name, like “mybusiness.com,” to a specific IP address. Without an A record, your domain name would not know where to direct visitors.

colourful collage of abstract shapes and map with pin

How does an A record work

When someone enters your domain name into their browser, their device starts a process to locate your website. The device sends a request to a DNS server, asking for the IP address of your domain. The DNS server checks its records and finds the A record that matches your domain name. It then sends the IP address back to the browser, which uses it to connect to the right server.

The A record acts like an address book. It translates human-readable domain names into machine-readable IP addresses. This process is called DNS resolution. A records are especially important for ensuring fast and accurate connections between users and your website.

If you move your website to a new hosting provider with a different IP address, you must update the A record. This ensures users are directed to the correct server.

Understanding key components

An A record consists of a few simple components that make it function correctly.

  • Domain Name: This is the name you want to point to an IP address. For example, “mybusiness.com” or a subdomain like “blog.mybusiness.com.”
  • IP Address: This is the destination server’s address where your domain points. It’s typically an IPv4 address, such as 192.0.2.1.
  • TTL (Time to Live): This value determines how long DNS servers should cache the A record. Shorter TTL values allow faster updates but increase server load. Longer TTL values improve performance but delay changes.

Examples

Imagine you own a small business and set up a website using the domain “bakeshop.com.” The A record for your domain points to the IP address of your hosting provider’s server, such as 203.0.113.45. When customers visit “bakeshop.com,” their browser uses the A record to find and display your website.

A records are also used for subdomains. If you want a subdomain like “shop.bakeshop.com” to point to a specific server, you create an A record for it. This can direct traffic to a different IP address if needed, allowing flexibility in how your domain is managed.

Some hosting providers use A records in combination with other DNS records, like CNAME records, to deliver advanced functionality while keeping things simple for domain owners.

How to check your A records

Checking your A records is essential for troubleshooting or ensuring that your domain points to the right server. You can access your A records through your domain registrar or DNS hosting provider. Log into their platform and look for the DNS management section, often called “DNS Settings.”

In this section, you’ll find a list of all DNS records associated with your domain. Look for entries labeled as “A.” These will show the domain name, the IP address it points to, and the TTL.

If you prefer external tools, services like MXToolbox or WHOIS lookup can display A records. These tools allow you to quickly verify that your domain resolves to the correct IP address.

Common problems and how to fix them

While A records are straightforward, issues can arise that disrupt your website’s functionality. Understanding these problems helps keep your domain running smoothly.

  • Incorrect IP Address: If the A record points to the wrong IP address, visitors will be directed to the wrong server or see an error. Double-check the IP address provided by your hosting provider.
  • Conflicts with Other DNS Records: Conflicting records for the same domain can cause resolution failures. For example, having both an A record and a CNAME record for “www.mybusiness.com” is not allowed. Resolve conflicts by using one type of record per domain.
  • Propagation Delays: Changes to A records can take time to propagate across the internet. This delay can cause temporary issues. Plan updates during low-traffic periods to minimize impact.
  • Expired TTL Settings: If TTL values are set too low, DNS servers might not cache the record long enough, increasing lookup times. Adjust TTL to balance speed and efficiency.