Quick answer
How do I point a domain to a server IP?
To point a domain to a server IP at Shroudname, open the domain's DNS tab, click Add record, choose type A, enter @ as the name and the server's IPv4 address as the value, then add www the same way and click Save changes. An IPv6 server takes an AAAA record. Most resolvers follow within the TTL, 1 hour by default.
In brief
- A record: name @ (the domain itself), value the server's IPv4 address.
- www: a second A record, or a CNAME pointing to the bare domain.
- IPv6: an AAAA record with the same names, if the server has one.
- Save: nothing is sent until Save changes; the table shows each row as New, Edited or Deleted first.
- Conflicts: web forwarding on a host replaces its A, AAAA and CNAME records, so use one or the other.
What are the steps in the DNS tab?
Six steps, for a domain on Shroudname's nameservers. If the domain uses another provider, the same records are created there instead.
Open the DNS tab
In My domains, click Manage on the domain, then DNS. The table is titled DNS records and lists what is already set.
Click Add record
The form Add a DNS record opens. Choose A in Type. In Name, type @, which stands for the domain itself.
Enter the IPv4 address
Paste the server's address in IPv4 address, such as 203.0.113.10, keep the TTL or pick 5 min during a move, and click Add.
Add www
Add a second record: either A with name www and the same IP, or CNAME with name www pointing to the bare domain.
Add AAAA if the server has IPv6
Same names, type AAAA, value the IPv6 address. Skip it if the host gave no IPv6 address.
Click Save changes
The bar reads Unsaved DNS changes until you save. After saving, DNS records saved confirms it and the History tab keeps the request.
Which record type should you use?
The record depends on what the host gives you: an IP address calls for A or AAAA, a host name calls for CNAME or ALIAS.
| Host gives you | Record | Name | Note |
|---|---|---|---|
| An IPv4 address | A | @ and www | The common case for a VPS or dedicated server |
| An IPv6 address | AAAA | @ and www | Add it next to the A record, not instead |
| A host name, for www | CNAME | www | A CNAME cannot sit on @ |
| A host name, for the bare domain | ALIAS | @ | Like a CNAME, but allowed on the domain itself |
| A platform such as Vercel or Netlify | Template | @ and www | Templates menu fills the records |
Why use @ and www?
@ is the bare domain, example.com, and www is a separate name, www.example.com; visitors type both, so both need a record. In the DNS standard of RFC 1035, an A record maps one name to one IPv4 address, and nothing links the two names unless you create both.
A CNAME on www is the tidy choice: when the server's IP changes, only the A record on @ needs editing. RFC 1034 forbids a CNAME next to other records on the same name, which is why it cannot sit on @, where the zone also holds NS records. The ALIAS type exists for that case, when a platform gives a host name for the bare domain.
So how to point a domain to a server IP comes down to two rows in the table, one per name, plus an AAAA row for each if the server has IPv6. If you only want the name to send visitors to another site, forwarding is simpler than a server: see how to forward a domain to another URL.
Does pointing a domain make the server IP public?
Yes: an A record is public by design, and anyone can query it, so the server's IP becomes visible the moment you point a domain to a server IP. This is separate from the registrant data, which WHOIS privacy keeps out of view.
Three practical notes:
- Reverse DNS (the PTR record that maps the IP back to a name) is set at the server's host, not at the registrar.
- A reverse proxy or CDN in front of the server shows its own IP in the A record instead of the server's.
- Mail sent from that server needs SPF and often reverse DNS set by the host; mail received on the domain is a separate topic, in how to set up a private email on your own domain.
According to Shroudname's survey of 12 November 2026, three years of a .com cost $37.47 at Shroudname against $42.31 on average at Namecheap, Dynadot, GoDaddy, Cloudflare and Njalla, with DNS hosting included at no extra cost.
How do you check that the domain points to the right IP?
Ask a public resolver for the record: dig A example.com, or nslookup example.com on Windows, should return the IP you entered. If an old IP comes back, a resolver still holds the previous answer until its TTL expires. That check is the last step of how to point a domain to a server IP, and the first one to repeat whenever the site seems to vanish.
A clean move goes in this order:
- A day before, lower the TTL of the existing records to 5 min and save.
- On moving day, change the IP and save.
- Once traffic reaches the new server, raise the TTL back to 1 hour or more.
If the DNS tab shows This domain uses other nameservers, the records here are not served; switch back or edit them at the provider, as explained in how to change nameservers on a private domain. A host that asks to prove ownership first wants a TXT record, covered in how to verify domain ownership with a TXT record.
Frequently asked questions
How long does it take for a new A record to work?
A brand-new name usually answers within minutes of Save changes. Changing an existing record takes up to the old TTL, as resolvers drop their cached answer.
Should www be a CNAME or an A record?
Either works. A CNAME to the bare domain means one IP to edit later; an A record avoids one extra lookup. The best choice for most single-server sites is the CNAME.
Can I point the domain to a server IP and keep email forwarding?
Yes. Email uses MX records and the A record serves the website, so both live side by side in the same zone.
What TTL should I set?
1 hour suits a stable server; 5 min suits the day of a move. The form accepts presets from 5 min to 1 day, or a custom value.
My host gave nameservers, not an IP. What now?
Then change the nameservers on the Nameservers tab instead of adding records; the host will run the DNS.
Verdict
- A on @, CNAME or A on www, Save changes: that is the whole job for one server with an IPv4 address.
- Lower the TTL before a move and check with dig: the old answer fades only as fast as its TTL allows.
Sources (3)
- RFC 1035: Domain Names, Implementation and Specification — IETF (read 2026-11-16)
- RFC 3596: DNS Extensions to Support IP Version 6 — IETF (read 2026-11-16)
- RFC 1034: Domain Names, Concepts and Facilities — IETF (read 2026-11-16)
Point your domain
Free DNS hosting with A, AAAA, CNAME and ALIAS records, edited from the DNS tab.