How to Point a Domain to Hosting or a VPS (Step by Step)

Prices checked Oct 31, 2026Hands-on tested Oct 31, 2026Updated Oct 31, 2026

FindNChoose is reader-supported. Some links may earn us a commission at no cost to you; it never changes our verdicts. How we make money · How we test

What we did ourselves

We moved FindNChoose from Hostinger shared hosting to our own VPS in 2026 using the second method. We kept DNS at Hostinger, changed the A and AAAA records for the root domain and www to the VPS, removed the old CDN records, and left every email and verification record untouched. We saved a snapshot of the DNS zone first so we could roll back in one step. The VPS steps below follow what we did, plus general best practice such as lowering the TTL in advance, which is marked as optional; we have left out our real IP addresses.

Nameservers vs DNS records: which should you change?

Every domain has nameservers: the servers that answer the question “where is this domain?” The nameservers hold the DNS zone, which is the list of records (A, AAAA, CNAME, MX, TXT and so on). You can either hand the whole zone to your host by changing the nameservers, or keep the nameservers where they are and edit individual records.

	Change nameservers	Edit A/AAAA/CNAME records
What changes	Who controls the whole DNS zone	Only where the website points
Best for	Shared or managed hosting that sets everything up for you	VPS, cloud servers, sites with existing email
Email risk	High: existing MX and TXT records are lost unless you recreate them at the new host	Low: email records stay as they are
Speed of change	Can take up to 24 to 48 hours	Usually minutes to a few hours, depending on TTL
Rollback	Change nameservers back and wait again	Restore the old record values

If you are not sure what the difference between a domain and a URL is, read URL vs domain name first.

The DNS records you need to know

A record: points a name to an IPv4 address (for example, the root domain “@” to your server).
AAAA record: the same for an IPv6 address. Add it only if your server really answers on IPv6; a wrong AAAA record breaks the site for visitors on IPv6 networks.
CNAME record: points one name to another name, commonly “www” to the root domain or to a host-provided address. A CNAME cannot sit on the root domain at most DNS providers.
MX records: where email for the domain is delivered.
TXT records: text values used for SPF (which servers may send your email), DKIM (email signatures), DMARC (email policy) and site verification for Google Search Console and other services.
TTL (time to live): how many seconds resolvers may cache a record. A lower TTL means changes are picked up sooner.

How to point a domain to hosting with nameservers

This is the usual route for shared hosting such as Hostinger or Bluehost.

Add the domain in your hosting panel first, so the host creates the website and a DNS zone for it.
Copy your current DNS records, especially MX and TXT records, if the domain already has email or verification records. Take a screenshot or export the zone.
Find the host’s nameservers in its dashboard (they look like ns1.examplehost.com and ns2.examplehost.com).
At your registrar, replace the nameservers with the host’s. Remove any old ones.
Recreate the email and verification records in the host’s DNS zone if the host did not import them.
Wait for propagation, then issue or confirm the free SSL certificate in the hosting panel.

Note: some registrars, such as Cloudflare Registrar, require you to keep their nameservers. In that case, use the records method below. Our registrar comparison lists these conditions.

How to point a domain to a VPS with A and AAAA records

This is what we did for this site, and it is the method we recommend for a VPS.

Build the site on the server first. We built ours on a temporary, non-indexed staging subdomain so visitors never saw a half-finished site. See how to move WordPress to a VPS.
Save a copy of the DNS zone. Our DNS provider supports zone snapshots, which made rollback a single restore. If yours does not, export or screenshot every record.
Optional: lower the TTL on the records you will change (for example, to 300 seconds) a day ahead, if your provider allows it. That shortens the time old answers stay cached.
Change the A record for “@” to the VPS’s IPv4 address, and the AAAA record to its IPv6 address if the server is set up for IPv6.
Point “www” to the same server, either with its own A/AAAA records (what we did) or a CNAME to the root domain.
Remove records that point to the old host, such as CDN or proxy records for the website. Two conflicting A records mean some visitors reach the old site.
Leave email records alone. MX, SPF, DKIM and DMARC records do not depend on where your website is hosted.
Issue the SSL certificate on the server once the domain resolves to it. We used Let’s Encrypt through CloudPanel for both the root domain and www.
Test, then keep the old hosting for a few days as a fallback.

Keep the old website untouched until you are confident in the new one. We left the old shared-hosting site in place, so rolling back would only have meant restoring the DNS snapshot.

Which email records to keep (and why)

Record	Typical host name	What breaks if it is lost
MX	@	Incoming email stops arriving
SPF (TXT)	@	Your outgoing email is more likely to land in spam
DKIM (TXT or CNAME)	selector._domainkey	Email signatures fail; deliverability drops
DMARC (TXT)	_dmarc	Receivers lose your policy; spoofing is easier
Verification (TXT)	@ or a special name	Google Search Console and other services may lose verification

If your website will now send email itself (for example, contact-form notifications from a VPS), add the server to your SPF record or, better, send through an email provider that you have already authorized.

Propagation: how long it takes and how to check

Record changes are visible as soon as resolvers’ cached copies expire, which depends on the old TTL. With short TTLs, many visitors see the change within minutes; with long TTLs or a nameserver change, it can take up to a day or two. To check:

Run nslookup yourdomain.com or dig yourdomain.com A and compare the answer with your server’s IP.
Check both the root domain and www, and both IPv4 and IPv6.
Look at the response headers in your browser’s developer tools to confirm which server answered.
Clear your browser cache or use a private window if you still see the old site.

Common mistakes

Changing nameservers and losing email records. Copy them first.
Adding an AAAA record for a server that is not set up for IPv6. Some visitors will get errors.
Forgetting www. Point it to the server and redirect one version to the other.
Issuing SSL too early. Let’s Encrypt validation fails until the domain resolves to the new server.
Leaving old CDN or proxy records that still send traffic to the previous host.

Still choosing hosting? Compare options in shared hosting vs VPS and size a server with the VPS sizing calculator.

Frequently asked questions

Should I change nameservers or DNS records?

Change the nameservers if you want your host to manage all DNS and you have no email or verification records to keep. Edit the A, AAAA and CNAME records if you are moving to a VPS or already use email on the domain, because the rest of the zone stays untouched.

How long does it take to point a domain to hosting?

Record changes usually take effect within minutes to a few hours, depending on the TTL. Nameserver changes can take up to 24 to 48 hours to reach everyone.

Will pointing my domain to new hosting break my email?

Not if you keep the MX, SPF, DKIM and DMARC records. They are independent of the website, so editing only the A, AAAA and www records leaves email working.

Do I need both an A and an AAAA record?

You need an A record. Add an AAAA record only if your server is configured to serve the site over IPv6; otherwise, leave it out.

Can I point a domain to a VPS without moving the domain?

Yes. You keep the domain at your registrar and only change the A and AAAA records to the VPS’s IP addresses. There is no need to transfer the domain.

Sources

FindNChoose Editorial Team

We run our own WordPress sites on shared hosting and on a VPS, and use AI coding tools every day. We publish what we measured, list every price with the date we checked it and label anything we have not tested ourselves. About us · Editorial policy