How to Point a Domain to Your Server (A Record)

  • domain not pointing
  • DNS not propagating
  • A record
  • 7 min read
  • Updated 7 October 2026
  • ESAGAMES Team

Pointing a domain to a server comes down to one DNS record — the A record. Here's how it works, how to set it, and why it isn't instant.

Quick answer

To point a domain to your server, create an A record in the domain's DNS: name @ (and another for www) with your server's IPv4 address as the value. Changes usually work within minutes to a few hours, but can take up to 24–48 hours to reach everyone because of DNS caching.

How DNS actually works

When someone types your domain, their computer asks DNS "what IP is this?". An A record answers with your server's IPv4 address (an AAAA record does the same for IPv6). Point the A record at your server's IP and the domain reaches it.

Step 1: find your server IP

Your host shows it in the panel or welcome email. It looks like 217.156.22.2.

Step 2: set the A record

In your domain's DNS settings (at the registrar or host that controls the nameservers), create/edit:

Type   Name   Value            TTL
A      @      217.156.22.2     3600
A      www    217.156.22.2     3600

@ means the root domain (example.com); www covers the www subdomain.

Nameservers vs DNS records

DNS records only take effect where the nameservers point. If your domain uses your registrar's nameservers, edit the records there — not at the host. Check which nameservers are active before editing.

Step 3: wait for propagation

DNS changes are cached around the world based on the record's TTL, so they aren't instant — anywhere from a few minutes to a few hours (occasionally up to 24–48h). Lowering the TTL before a planned change makes the switch faster.

Check if it worked

# Linux/macOS
dig +short example.com
# Windows
nslookup example.com

If it returns your server IP, the A record is live. If it still shows the old IP, propagation isn't complete yet.

One A record pointed at your server IP is all it takes — the only catch is propagation, which is just DNS caches around the world catching up.

Common A record mistakes that stop it working

  • Editing records at the wrong nameservers — check which nameservers your domain actually uses before touching anything.
  • Leaving an old A record with a different IP still active, which can conflict with the new one.
  • Using a CNAME on the root domain (@) instead of an A record — most DNS providers block or mishandle this.
  • Typos in the IP address — copy-paste the IP rather than retyping it.
  • Forgetting the www A record (or CNAME), leaving www.example.com unreachable even though the root works.

How to prevent DNS and A record problems

Lower the TTL a day before any planned IP change so the old record expires from caches quickly, keep a written record of your current DNS settings before editing anything, and always verify with dig or an online propagation checker before assuming something's broken — most "it's not working" reports are just propagation still catching up.

If the domain resolves to nothing at all, see DNS_PROBE_FINISHED_NXDOMAIN. If the browser hangs instead of erroring, read ERR_CONNECTION_TIMED_OUT. Check whether a domain is available or taken with our domain search, and once DNS is live, secure it with SSL / Let's Encrypt renewal.

Frequently asked questions

How long does DNS propagation take?

Usually minutes to a couple of hours, but it can take up to 24–48 hours worldwide. It depends on the record's TTL and how aggressively networks cache it. Lowering TTL beforehand speeds up future changes.

What's the difference between an A record and nameservers?

Nameservers decide which server holds your DNS records; the A record is one of those records, mapping the domain to an IP. You must edit records at whichever nameservers your domain currently uses.

Should I use an A record or CNAME?

Use an A record to point a domain to an IP address. Use a CNAME to point one hostname at another hostname (e.g. www → example.com). The root domain (@) should normally be an A record.

Why does my domain show the old site after I changed the A record?

Almost always caching — either DNS propagation hasn't finished, or your own browser/OS is holding a cached DNS lookup. Try a different network or device, or flush your local DNS cache, before assuming the record is wrong.

Can I point a domain to an IP without changing nameservers?

Yes, as long as you edit the A record at whichever nameservers your domain already uses — you only need to touch nameservers if you're moving DNS management somewhere else entirely.

What happens if I have two A records with different IPs for the same name?

DNS will return both, and resolvers pick one somewhat unpredictably (often round-robin). This causes intermittent, hard-to-diagnose failures — remove the outdated one so only the correct IP remains.

Do I need both an A record and an AAAA record?

Only if your server has a public IPv6 address you want to use. Without an AAAA record, IPv6-capable visitors simply fall back to the A record (IPv4), so an A record alone is enough for most setups.

Go deeper on this

Guides and explainers that pair with this fix — from our guides and blog.

Related articles

Skip the troubleshooting

Managed, protected hosting in Frankfurt — we handle the Linux, the network and the DDoS so you don't have to.

Game hosting All articles