# Point a domain to your server

> Connect your domain to a HyperDC VPS, dedicated server or hosting plan: set A and AAAA records or change the nameservers, add www and check the result with dig.

Difficulty: Beginner\
Tested on: HyperDC client area, Ubuntu 24.04 LTS, Windows 11, macOS Tahoe 26

Your domain and your server meet in DNS: an A record (and an AAAA record for IPv6) tells the world which IP address serves `example.com`. This guide shows both ways to set it up and how to check that it worked. Replace `example.com` and `203.0.113.10` with your domain and your server's address.

## Before you start

- Find your server's IP address: **Services › My Services**, open the service, **Server Information** (**Primary IP**). For hosting plans, the welcome email lists the nameservers or the IP address.
- Find out where your domain's DNS is hosted now:

```bash
dig NS example.com +short
```

On Windows use `Resolve-DnsName example.com -Type NS`. The answer names the current DNS host.

## Option A: Change the A and AAAA records

Use this when you keep your current DNS host (your registrar, Cloudflare or another provider).

1. Sign in to your DNS host and open the zone of `example.com`.
2. Create or edit these records:

| Type | Name | Value | TTL |
|---|---|---|---|
| A | `@` (the root) | `203.0.113.10` | 300 |
| A or CNAME | `www` | `203.0.113.10` or `example.com` | 300 |
| AAAA | `@` | your server's IPv6 address (only if it has one) | 300 |

3. Remove old A or AAAA records for the same names that point elsewhere.
4. Leave MX and TXT records alone unless your email moves too.

## Option B: Change the nameservers

Use this when you want the new DNS host, for example your hosting plan's control panel, to manage the whole zone.

1. Prepare the zone at the new DNS host first, with every record you need: website, `www`, MX, SPF, DKIM, DMARC and verification records.
2. For a domain registered with HyperDC: **Domains › My Domains › Manage Domain › Nameservers**, choose **Use custom nameservers (enter below)**, enter the new nameservers and select **Change Nameservers**. At another registrar, use its nameserver setting.
3. If the domain used DNSSEC at the old DNS host, remove the old DS record at the registrar before switching, or the domain stops resolving for validating resolvers.

## Verify the result

Ask public resolvers and your authoritative nameserver:

**Linux and macOS**

```bash
dig example.com A +short
dig www.example.com A +short
dig example.com AAAA +short
dig example.com A @1.1.1.1 +short
```
**Windows**

```powershell
Resolve-DnsName example.com -Type A
Resolve-DnsName www.example.com -Type A
Resolve-DnsName example.com -Type AAAA
Resolve-DnsName example.com -Type A -Server 1.1.1.1
```

**Verify:** each answer returns your server's address. If public resolvers still show the old address, wait for the old TTL to expire; your authoritative nameserver must already show the new one.

Then test the website itself:

```bash
curl -I http://example.com
```

A response such as `HTTP/1.1 200 OK` or a redirect means the server answers for your domain.

## Configure the server and add HTTPS

The server must know about the domain too:

- **Web hosting:** add the domain in the control panel if it is not the plan's main domain.
- **Your own server:** configure a virtual host (nginx `server_name` or Apache `ServerName`/`ServerAlias`) for `example.com` and `www.example.com`.

Then add a certificate: [install an SSL certificate](/guides/install-ssl-certificate). Free certificates validated over HTTP can only be issued once the domain points to the server.

## Troubleshooting

**Some visitors see the old site.** Their resolver cached the old record. Wait for the old TTL to pass.

**The domain works, `www` does not.** Add the `www` record from the table above.

**IPv6 visitors reach the wrong server.** An old AAAA record still exists. Remove it or point it to your server's IPv6 address.

**The domain stopped resolving after a nameserver change.** The new zone is missing records, or an old DS record remains. See [DNS not resolving](/guides/dns-not-resolving).

## Next steps

- Understand the records: [DNS basics for a new domain](/guides/dns-basics-for-a-new-domain).
- Secure the site: [install an SSL certificate](/guides/install-ssl-certificate).
- Add a CDN in front: [Cloudflare in front of your site](/guides/cloudflare-proxy-setup).

## Frequently asked questions

### Do I have to transfer my domain to HyperDC first?

No. A domain can stay with any registrar. You only change its A and AAAA records, or its nameservers, to point to your HyperDC service.

### Which is better: changing records or changing nameservers?

Changing the A and AAAA records is quicker and keeps your other records, such as email, untouched. Changing nameservers moves the whole zone to a new DNS host, which then must hold every record you need.

### How long until the domain works?

Record changes reach most visitors once the old TTL has expired, often within minutes to an hour. Nameserver changes can take up to a day or two.

### Which nameservers do I use for web hosting?

The ones in your hosting welcome email. With them, the hosting control panel manages all records, including email.

### Do I need an AAAA record?

Only if your server has an IPv6 address and your site works on it. A wrong or outdated AAAA record sends IPv6 visitors to the wrong place, so remove AAAA records you do not use.

---

Source: <https://hyperdc.com/guides/networking/point-domain-to-server>\
Updated: 2026-10-09