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

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.

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.

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.

Related domain and hosting guides

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 domain and nameserver status with our domain checker, and once DNS is live, secure it with SSL / Let's Encrypt renewal.