Last updated:
No A record: what it means and how to fix it
Your domain does not have an A record, which means it cannot resolve to an IPv4 address. Visitors trying to reach your website will see "server not found" in their browser. Your site is effectively offline. An A record is one of the most fundamental DNS records, and without one (or a CNAME that resolves to one), there is no address for browsers to connect to.
- Confirm the record is missing. Run this command to check:
If the ANSWER section is empty, there is no A record.
- Find your server's IP address. Check your hosting provider's dashboard for the IPv4 address of your web server.
- Log in to your DNS provider (Cloudflare, Route 53, GoDaddy, Namecheap, or similar).
- Add a new A record with these settings:
| Host / Name | Type | Value | TTL |
|---|---|---|---|
| @ | A | 203.0.113.50 | 3600 |
Replace 203.0.113.50 with your actual server IP address.
- Verify the record is live:
You should now see your IP address in the ANSWER section. If you use a hosting platform like Vercel or Netlify, you may need a CNAME record instead. Check your provider's documentation.
What is an A record
An A record is the most fundamental DNS record type. It maps your domain name to an IPv4 address, telling browsers and other clients exactly where to find your server. When someone types your domain into a browser, the first thing that happens is a DNS lookup for the A record.
The "A" stands for "Address". Without this record, the DNS lookup will succeed (the domain exists and nameservers respond), but there is no IP address to connect to. The result is the same as if the server did not exist.
How DNS uses A records to load your site
When a visitor types your domain into their browser, a chain of lookups occurs. The A record is the final, critical link in that chain.
Compare this with a working setup: the nameserver returns an IP address (e.g. 203.0.113.50), the browser connects to that address, and the website loads. Without the A record, this chain breaks at the DNS level before a connection is even attempted.
How to think about this (simple)
If you are not familiar with DNS, here is the simplest way to understand this issue:
- Your domain name is like a street name. The A record is the house number.
- Without a house number, the postman knows the street exists but has nowhere to deliver.
- Browsers work the same way. They know your domain name, but without the A record, they have no address to connect to.
- Adding an A record is like putting the house number on the door. Once it is there, traffic flows normally.
This is different from a DNS lookup failure, where the entire DNS system is unreachable. With a missing A record, DNS works, but there is simply no address record to return.
How to tell if this is your issue
These are common signs that a missing A record is the cause of your problem:
- Your website shows "server not found". The browser cannot resolve the domain to an IP address. This is different from a timeout or 500 error, which mean the server was found but could not respond.
- Your domain was flagged for having no A record. A domain health scan or DNS audit reported a missing A record specifically.
- You recently migrated DNS providers. If you switched from one DNS provider to another and forgot to recreate the A record at the new provider, the record will be missing.
- A dig query returns an empty answer. Running dig yourdomain.com A returns a response but the ANSWER section is empty (no IP address).
- Email still works but the website does not. Email uses MX records, not A records. If email is fine but the website is down, a missing A record is a likely cause.
Quick check: Run dig yourdomain.com A @8.8.8.8. If the ANSWER section is empty, you have no A record. If the command returns SERVFAIL or a timeout, the issue is a DNS lookup failure, not a missing A record.
Without an A record vs with one
Without an A record
- Website is completely unreachable
- Browser shows "server not found"
- APIs and services on the domain fail
- Search engines cannot crawl your site
- SSL certificates cannot be validated
With an A record
- Domain resolves to your server's IP
- Website loads normally for visitors
- APIs and services are accessible
- Search engines can index your pages
- SSL/TLS works as expected
Why this matters
A missing A record does not just make your website unavailable. It has cascading effects across your entire online presence:
- Website completely offline. This is not a degraded experience. Visitors cannot reach your site at all. There is no IP address for the browser to connect to, so the connection is never attempted.
- API and service failures. Any application, webhook, or third-party integration that connects to your domain by name will fail. This includes payment callbacks, CRM integrations, and monitoring endpoints.
- SEO damage. Search engines cannot crawl pages they cannot reach. If the A record is missing for more than a few days, Google may begin deindexing your pages. Recovering rankings after a prolonged outage can take weeks.
- SSL certificate issues. Certificate authorities need to reach your domain to issue or renew SSL certificates. A missing A record will cause certificate renewals to fail, compounding the problem when the record is restored.
- Subdomains may also be affected. If subdomains (like www, app, or api) rely on the root domain's A record through CNAME chains, they will also stop resolving.
- Email may still work. Email delivery uses MX records, not A records. Your domain can receive email without an A record. However, webmail login pages hosted on your domain will be inaccessible.
How to fix it properly
Work through these steps in order. The right approach depends on how your site is hosted.
Step 1: Confirm the A record is truly missing
Before making changes, verify that the A record is actually missing and not just delayed by propagation:
If neither an A nor a CNAME record exists, proceed to step 2. If a CNAME exists, the issue may be with the target hostname it points to, not a missing A record.
Step 2: Identify your server's IP address
You need the IPv4 address of your web server or hosting provider. Where to find it depends on your setup:
- VPS or dedicated server (DigitalOcean, Linode, AWS EC2): the IP is shown in your server's dashboard.
- Cloudflare (proxied): create the A record pointing to your origin server IP. Cloudflare handles the rest.
- Platform hosting (Vercel, Netlify, Render): these providers typically use CNAME records instead of A records. Check their documentation for the correct hostname value.
- Shared hosting (cPanel, Plesk): check the hosting dashboard or contact support for the correct IP address.
Step 3: Log in to your DNS provider
Access the DNS management panel for your domain. This might be at your registrar (GoDaddy, Namecheap) or a dedicated DNS provider (Cloudflare, Route 53, DNS Made Easy). Make sure you are editing the correct domain.
Step 4: Add the A record
Create a new DNS record with these settings:
| Field | Value |
|---|---|
| Host / Name | @ |
| Type | A |
| Value / Points to | Your server's IPv4 address |
| TTL | 3600 (or Auto) |
The @ symbol represents the root domain (e.g. yourdomain.com without any subdomain prefix).
Important: If you use a platform like Vercel or Netlify, do not add an A record. Follow their documentation to add a CNAME record instead. Adding the wrong record type will cause your site to not load correctly.
Step 5: Add a www record
Many visitors will type www.yourdomain.com. Add a second record to handle this:
| Host / Name | Type | Value |
|---|---|---|
| www | CNAME | yourdomain.com |
This ensures www.yourdomain.com resolves by following the CNAME to your root domain's A record.
Step 6: Verify the record is working
Wait a few minutes, then test:
If you see your IP address in the ANSWER section, the record is live. Most DNS changes take effect within minutes, but full global propagation can take up to 48 hours. If the record does not appear after an hour, double-check that your nameservers at the registrar match your DNS provider.
A record vs CNAME: which one do you need?
Both A records and CNAME records can make your domain resolve to a server. They work differently, and choosing the wrong one is a common source of confusion.
| A Record | CNAME Record | |
|---|---|---|
| Points to | An IPv4 address (e.g. 203.0.113.50) | A hostname (e.g. mysite.netlify.app) |
| Lookup steps | One (direct to IP) | Two or more (hostname, then its A record) |
| Root domain | Works at the root (@) | Not supported by all providers at root |
| IP changes | Must be updated manually | Updates automatically (follows target) |
| Best for | Servers with static IPs | Platform hosting (Vercel, Netlify, Heroku) |
When to use an A record:
- You have a server with a fixed IP address (VPS, dedicated, EC2)
- You need a record at the root domain and your provider does not support CNAME flattening
- You are behind Cloudflare (set the A record to your origin IP, Cloudflare proxies automatically)
When to use a CNAME instead:
- Your hosting provider gives you a hostname, not an IP (e.g. Vercel, Netlify, Render, Heroku)
- You want the record to automatically follow IP changes at the target
- You are setting up subdomains (www, app, api) that should follow the root domain
CNAME at the root domain: Some DNS providers (like Cloudflare and Route 53) support "CNAME flattening", which lets you use a CNAME at the root domain. If your provider does not support this, you must use an A record at the root.
Common mistakes
- Wrong IP address. Pointing to an old or incorrect IP means the domain resolves but leads to the wrong server (or nowhere). Double-check the address with your hosting provider.
- CNAME at the root without flattening. Some DNS providers do not allow a CNAME at the root domain because it conflicts with other record types like MX and TXT. Use an A record at the root, or switch to a provider that supports CNAME flattening (Cloudflare, Route 53).
- Forgetting the www subdomain. Adding an A record for @ but not for www means www.yourdomain.com will not resolve. Add a CNAME for www pointing to the root domain.
- Accidentally deleted during DNS migration. When moving DNS providers, A records can be lost if the zone is not fully recreated. Always export your DNS zone before migrating, and verify all records at the new provider.
- Using a CNAME when an A record is needed. If your hosting provider gives you an IP address (not a hostname), you need an A record. Adding a CNAME with an IP address as the value will not work.
- Propagation confusion. After adding an A record, it can take minutes to hours to propagate globally. Test with dig @8.8.8.8 (bypasses cache) before concluding the record is not working.
How 1Pane detects this
During a domain health scan, 1Pane queries for A records at your root domain. If the DNS lookup succeeds but the response contains no A record and no CNAME record, the scan flags this as a critical issue. This distinguishes it from a DNS lookup failure (where the entire lookup fails) and from a working setup that uses CNAME instead of A records.
1Pane also checks for related records that may be affected, including SPF and DMARC records. A missing A record is reported as a critical issue because it means the website is completely unreachable.
Frequently asked questions
What is the difference between an A record and a CNAME?
An A record maps your domain directly to an IPv4 address (e.g. 203.0.113.50). A CNAME maps your domain to another hostname (e.g. mysite.netlify.app), which then resolves to an IP via its own A record. Both achieve the same result, but CNAMEs add an extra lookup step and cannot always be used at the root domain.
Can my email work without an A record?
Yes. Email delivery relies on MX records, not A records. Your domain can send and receive email without an A record. However, if your webmail login page is hosted on the domain, it will be inaccessible without an A record.
Do I need an A record if I use Cloudflare?
Yes. Even with Cloudflare proxying enabled, you need an A record pointing to your origin server. Cloudflare intercepts the traffic and routes it through its network, but the A record must exist in your Cloudflare DNS zone for this to work.
My A record is correct but my site still does not load. What is wrong?
If the A record resolves correctly but the site does not load, the issue is with the server, not DNS. Common causes include the server being offline, a firewall blocking port 80/443, the web server software not running, or an expired SSL certificate. Check your server logs and hosting dashboard for errors.
Related issues
A missing A record is often found alongside these other domain health issues:
Scan your domain with 1Pane to check for missing A records, DNS issues, and email authentication problems in one place.
Scan your domain with 1Pane