Skip to content

Pointing your domain to your hosting or VPS

Updated 26 Oct 2026

A domain only shows your website once its DNS tells browsers where the site lives. How you do that depends on where the site is hosted and where the domain is registered.

Option 1: change the nameservers (shared hosting)

This is the easiest choice for shared hosting, because the hosting server then manages every record for you, including email.

  1. Open your hosting service in the client area and note the two nameservers shown there.
  2. If the domain was registered with us, open it under Domains and enter those nameservers. If it is registered somewhere else, log in to that registrar and change the nameservers there.
  3. Save. The change usually spreads within a few hours, sometimes up to 24 to 48 hours.

Option 2: add DNS records (VPS or dedicated server)

For a VPS, keep the domain's current nameservers and add records that point to the server's IP address:

Type Name Value
A @ your server's IPv4 address
A www your server's IPv4 address

If the domain uses our nameservers, add these under DNS on the domain's page in the client area. Otherwise add them at the company that runs your DNS. Remove any older A records for the same names so visitors are not sent to two places.

Email records

If you use email on your own domain, the MX record decides where mail is delivered. With shared hosting and our nameservers this is set up automatically. If you use Google Workspace, Microsoft 365 or another provider, add the MX and TXT (SPF) records they give you.

Check that it worked

  • Visit your domain in a private browser window.
  • Run nslookup yourdomain.com (Windows) or dig yourdomain.com (macOS and Linux) and check that the IP address is the one on your service page.

If the old site still shows, your computer or ISP may have the old address cached. Wait a little, or try from mobile data.

Add HTTPS

On shared hosting, free SSL certificates are issued automatically once the domain points to the server. On a VPS, install a free certificate from Let's Encrypt, for example with certbot, after the A records are working.

Was this article helpful?