# How do you point a domain to a server?

> How to point a domain to a server: add an A record with the server's IPv4 (AAAA for IPv6) on @, a CNAME on www, and a low TTL (300 s) while testing.

- URL: https://tallyname.com/guides/how-to-point-a-domain-to-a-server/
- Last updated: 2026-11-16
- Publisher: Tallyname (https://tallyname.com)

Pointing a domain at a server means publishing its IP address in the domain's DNS. Two or three records do it; the details are which name gets which record and how long resolvers keep the old answer.

**Quick answer — How do you point a domain to a server?**

Here is how to point a domain to a server: add an A record on @ with the server's IPv4 address, an AAAA record for IPv6, and a CNAME on www. At **Tallyname** this is done in the free DNS tab of the client area, with a TTL from 60 to 86,400 seconds.

**In brief**

- **A record**: maps a name to an IPv4 address; **AAAA**: to an IPv6 address.
- **@ is the domain itself**, www a sub-domain; a CNAME cannot sit on @, so use A, AAAA or ALIAS there.
- **TTL** is how long resolvers may cache the answer; lower it before a move, raise it after.
- **Records only work on the active nameservers**: at Tallyname, the DNS tab is served when the domain uses Tallyname's nameservers.
- **Templates**: Vercel, Netlify, GitHub Pages, Cloudflare Pages and Shopify are preset in the DNS tab.

## Which DNS record points a domain to a server?

*DNS record types used to point a domain at a server, with the limits of Tallyname's DNS editor, read on 16 November 2026*

| Record | Points | Typical name | Note |
| --- | --- | --- | --- |
| A | A name to an IPv4 address | @ and www | Example value 203.0.113.10 |
| AAAA | A name to an IPv6 address | @ and www | One address per record |
| CNAME | A name to another host name | www | Must be the only record of its name; not on @ |
| ALIAS | A name to a host name, resolved to its addresses | @ | Tallyname's answer to the CNAME-at-apex limit |
| MX | Mail for the domain to a mail server | @ | Lower priority numbers are tried first |
| TTL | Cache time of each record | Every record | 60 to 86,400 seconds at Tallyname |

## How do you point a domain to a server at Tallyname?

1. **Open the DNS tab** — In My domains, click Manage, then DNS. If a banner says the domain uses other nameservers, set the records at that provider instead.
2. **Add the A record** — Click Add record, choose type A, Name @, paste the server's IPv4 address, and pick a TTL such as 5 min.
3. **Add AAAA if needed** — If the server has IPv6, add an AAAA record on @ with that address.
4. **Cover www** — Add a CNAME on www pointing to the domain, or an A record on www with the same IP.
5. **Save the changes** — Check the rows marked New, then click Save changes. The change gets a reference and shows in History.
6. **Raise the TTL later** — Once the site answers correctly, edit the records to a longer TTL, such as 1 hour or 1 day.

## What does an A record do?

**It tells resolvers which IPv4 address answers for a name.** RFC 1035 defines the A record as the address of a host, and RFC 3596 defines AAAA as a record that stores a single IPv6 address. A browser looking up the domain receives that address and connects to the server.

The name field decides which address is concerned. In Tallyname's editor, @ is the domain itself, and a word such as www or mail is a sub-domain. Most sites need two names: the bare domain and www. The bare domain takes A and AAAA records. The www name can take its own A record, or a CNAME pointing to the bare domain so both follow the same address.

A CNAME has one constraint that trips many setups. RFC 1034 states that if a CNAME is present at a node, no other data should be present, which rules it out on @, where the domain's NS and SOA records live. Tallyname's editor refuses a CNAME on @ and suggests an ALIAS record, which behaves like a CNAME but is resolved by the nameserver into ordinary addresses.

```dns
; Example records for a server at 203.0.113.10 / 2001:db8::10
@    300  IN  A      203.0.113.10
@    300  IN  AAAA   2001:db8::10
www  300  IN  CNAME  example.com.
```

## How long does it take for a domain to point to a new server?

**As long as resolvers keep the old answer, which is set by the TTL of the record they cached.** RFC 1035 defines the TTL as the time interval, in seconds, that a record may be cached before it should be discarded. A record changed from a TTL of 86,400 seconds can keep sending some visitors to the old address for up to a day.

The method that avoids that wait is to lower the TTL first. Set the existing records to 300 seconds, wait at least the old TTL, then change the address: the switch now spreads within minutes. Once everything works, raise the TTL again to reduce lookups. Tallyname's editor accepts 60 seconds to 1 day, with presets from 5 min to 1 day and a Custom value.

At Tallyname, saving creates a change request with a reference; the table shows it at once and History follows its status. Changing the nameservers is slower: the client area warns it can take up to 48 hours to reach every network, which is why moving records within the same DNS host is quicker than [changing nameservers](https://tallyname.com/guides/how-to-change-nameservers/ "How to Change Nameservers").

## Which is the best way to point a domain to a hosting platform in 2026?

**Use the platform's published records, ideally through a template, and keep the domain's DNS where you can edit it.** Tallyname's DNS tab has presets for Vercel, Netlify, GitHub Pages, Cloudflare Pages and Shopify. Each one fills the A, CNAME or ALIAS records the platform documents; you check the preview of records to add or replace, then save.

Where a platform asks you to delegate the whole domain instead, the choice is between its nameservers and your registrar's. Delegation hands every record to the platform; keeping Tallyname's nameservers keeps DNS, web and email forwarding and managed DNSSEC in one place. The DNS hosting is free with every domain: free DNS hosting with A, AAAA, CNAME, ALIAS, MX, TXT, NS, SRV and CAA records, managed DNSSEC, and your own nameservers if you prefer (2 to 13).

According to Tallyname's survey of 16 November 2026, Tallyname renews a .com for $11.59 against an average of $15.25 at the five crypto registrars surveyed, DNS included. Signing the zone once it is pointed is covered in [how to enable DNSSEC](https://tallyname.com/guides/how-to-enable-dnssec/ "How to Enable DNSSEC"), and moving a live site between registrars in [how to transfer a domain without downtime](https://tallyname.com/guides/how-to-transfer-a-domain-without-downtime/ "How to Transfer a Domain Without Downtime").

## Frequently asked questions

### Should I use an A record or a CNAME to point a domain to a server?

Use A (and AAAA) on the bare domain, because a CNAME cannot sit there. On www, either works; a CNAME to the bare domain keeps both in step.

### Why does my domain still show the old server?

Resolvers are serving the cached record until its TTL runs out. Lower the TTL before the next change, and check that the domain uses the nameservers where you edited the records.

### Can I point a domain to a server without changing nameservers?

Yes, if the current nameservers are the ones whose records you edit. At Tallyname, keep the default nameservers and add the A record in the DNS tab.

### What TTL is best when pointing a domain to a new server?

300 seconds during the change, then 1 hour to 1 day once it is stable. Tallyname accepts 60 seconds to 86,400 seconds.

### Is there a cheap way to host DNS for many domains?

Use the registrar's own DNS if it is free and complete. At Tallyname it is included with every domain, with up to 200 records per domain.

**Verdict**

- **A and AAAA on @, CNAME or A on www**, with a low TTL during the change.
- **Use Tallyname's DNS tab and templates** if the domain uses Tallyname's nameservers.
- **Edit at the DNS provider** if the domain is delegated elsewhere.

## Sources

1. [RFC 1035: Domain names, implementation and specification](https://www.rfc-editor.org/rfc/rfc1035) — IETF (read 2026-11-16)
2. [RFC 1034: Domain names, concepts and facilities](https://www.rfc-editor.org/rfc/rfc1034) — IETF (read 2026-11-16)
3. [RFC 3596: DNS extensions to support IP version 6](https://www.rfc-editor.org/rfc/rfc3596) — IETF (read 2026-11-16)

**Free DNS with every domain** A, AAAA, CNAME, ALIAS, MX, TXT and more, edited in the client area. [Search a domain](https://tallyname.com/app/domains/?q=&tld=com&from=guides-how-to-point-a-domain-to-a-server&lang=en)

---

Tallyname: Tallyname is a domain registration service paid in crypto that charges one price every year — the first year, each renewal and a transfer cost the same — and publishes a renewal price index of crypto-friendly registrars every month. It is run by DomaineGoat LLC (Panama); domains are registered through its ICANN-accredited registrar partner. A .com costs $11.59/year.
