Hosting · Guide
How to Point a Domain to Your WordPress Host
Short answer
To point a domain to your WordPress host, change the domain's nameservers to your host's nameservers, or point its A record at your host's server IP address. Then add the domain in your hosting panel so the host knows which site to serve. DNS can take up to 48 hours to spread, so copy your MX, SPF and DKIM records first and check that SSL works once the domain resolves.
Key takeaways
- Nameservers hand all DNS to your host. An A record keeps DNS at your registrar and only moves the website.
- Bluehost uses ns1.bluehost.com and ns2.bluehost.com as its nameservers.
- Copy MX, SPF and DKIM records before you switch nameservers, or your email stops.
- DNS can take up to 48 hours to spread to every network, though most visitors see it sooner.
- Add the domain in your hosting panel too, or the host will not know which site to show.
What does “pointing a domain” actually change?
Pointing a domain changes DNS so browsers ask your host for the site instead of the old one.
Three parts work together: the registrar holds the domain, DNS records say where each service lives, and the host serves the website files. Pointing the domain only changes the DNS part.
Your domain, hosting and DNS can sit with three different companies. The change always happens where DNS is managed, which is usually the registrar or the host.
A domain name itself never holds website files. That is why you can buy a domain in one place, host the site in another, and move either one without losing the other.
If you have not bought a domain yet, see how much a domain name costs before you pick a registrar.
If DNS is managed at Cloudflare, edits happen on the DNS Records page. Cloudflare's docs say you pick Add record, choose the record type, fill in the fields, and save.
Should you change nameservers or only the A record?
Change nameservers when you want the host to manage all your DNS, and change only the A record when you want to keep DNS where it is.
| Method | Who controls DNS | Best when | Watch out for |
|---|---|---|---|
| Nameservers | Your host | You want one place for site, email and DNS | Old DNS records stop working, so copy MX and TXT records first |
| A record | Your registrar | You run email or other services elsewhere | You must keep the IP current if the host changes it |
Hostinger's support guide calls nameservers the best option when you want the host to manage the DNS zone and use it for hosting and email.
Do not mix the two methods. If you change nameservers, edits made only inside the host panel will not control live traffic until DNS moves.
If your setup is simple and all your services will live on the host, nameservers are the easier choice. If email or other services already run elsewhere, the A record keeps them untouched.
Cloudflare's docs note that the TTL field sets how long a record stays valid, so it also sets how long updates take to reach visitors. A short TTL set a day before a move helps the new answer spread faster.
How do you point a domain with nameservers?
Replace the nameservers at your registrar with the ones your host gives you, then add the domain in your hosting panel.
- Find your host's nameservers in its panel or welcome email. Bluehost uses ns1.bluehost.com and ns2.bluehost.com.
- Log in to your registrar, open the domain's DNS or nameserver settings, and replace the current nameservers.
- Save, then add the domain to your hosting plan so the host knows to serve it.
- Wait for DNS to spread, then load the domain in a browser.
Bluehost's DNS guide says to allow up to 24 to 48 hours for propagation, though most visitors see the change sooner.
Copy every record from your old DNS zone before you switch: MX for email, SPF, DKIM and any TXT records that verify tools such as Search Console.
If the host offers a setup wizard, use it. Hostinger's guide notes that its wizard detects your current DNS provider and links straight to its login page.
WordPress.com uses three nameservers: ns1.wordpress.com, ns2.wordpress.com, and ns3.wordpress.com. Its support guide says to remove the old nameservers and set only those three values. Some registrars show only two boxes at first and reveal a third after you fill the first two.
How do you point a domain with an A record?
Point the domain's A record at your host's server IP address and add a CNAME so www follows the root domain.
- Find your server IP in your hosting panel. Bluehost lists it under Hosting, then Server Information.
- At your registrar, edit the A record for @ (the root) to that IP.
- Point the www CNAME at your root domain.
- Add the domain in your hosting panel and wait for DNS to spread.
Use this method when your current DNS provider already manages email or other services. Hostinger's guide notes that any domain you own can point to its hosting, wherever it is registered.
If the IP changes later, the A record must change too. Nameservers avoid that upkeep, which is one reason hosts suggest them.
An A record points a name at an IP address, while a CNAME points a name at another name. That is why www is usually a CNAME to the root domain rather than a second A record.
If your host changes your server IP later, update the Content value of the A record. Cloudflare's docs say to check your host's docs when you are unsure which IP to use.
How do you add the domain inside your hosting account?
Add the domain in your hosting panel before or right after the DNS change, or the host will not know which site to show.
Hostinger's guide lists the order: check the domain is active and under your control, add it to the hosting plan, then connect it with nameservers or an A record.
A domain registered at the same host is often attached already. A domain from another registrar needs the DNS step above plus this step in the panel.
If the panel shows the domain as parked or unassigned, attach it to the right WordPress install before testing. A parked domain shows a placeholder page instead of your site.
If you have no host yet, read how to choose WordPress hosting first. The panel steps differ a little by host, but the idea is the same everywhere.
Connecting a domain to WordPress.com needs a paid plan: its support guide lists Personal, Premium, Business, and Commerce plans. Free sites must upgrade before they can connect a domain they own.
How long until the domain starts working?
Most visitors see the new site within a few hours, but DNS can take up to 48 hours to reach every network.
The wait depends on the TTL value on your old records. A long TTL tells networks to keep the old answer longer, so lower it a day before the switch when you can.
Test with a fresh browser session or a mobile connection, since your own computer may cache the old DNS answer.
DNS changes spread from server to server, not all at once. Your neighbour may see the new site hours before you do, and that is normal.
For a deeper look at the wait, see how long DNS propagation takes.
WordPress.com says activation can take up to 72 hours before the domain works fully on the new site. During that time, your old site may still load at the domain, while the free wordpress.com address keeps working.
How do you check the domain and SSL after the change?
Load the domain with and without www, check that https works, and confirm WordPress shows the right address in Settings, then General.
- Open http://yourdomain.com and https://yourdomain.com and confirm both reach the site.
- Open a post and a page to confirm links and images use the new domain.
- Check Settings, then General, and confirm the WordPress Address and Site Address match the domain.
- If the address is wrong, WordPress.org's Moving WordPress guide shows how to fix siteurl and home in the database.
SSL usually appears on its own once the domain resolves. If the padlock is missing after a day, ask the host to check the certificate.
If you use Cloudflare in front of the site, check its SSL mode too. See how to set up Cloudflare for WordPress.
WordPress.com issues a free SSL certificate once the domain status turns Active. The certificate usually takes a few minutes but can take up to 24 hours, and visitors may see a warning until it is ready.
What mistakes should you avoid?
These five mistakes cause most domain pointing failures.
- Changing nameservers without copying MX, SPF and DKIM records, which stops your email.
- Pointing the A record at an old or wrong IP address.
- Editing DNS at the registrar while the nameservers point at the host, so the edits never go live.
- Leaving DNSSEC turned on when the host asks for it off.
- Testing only on your own computer, which may still hold the old DNS answer.
Hostinger's support guide lists one more check before pointing: DNSSEC must be disabled on the domain.
If the browser reports that the domain cannot be found, see how to fix DNS_PROBE_FINISHED_NXDOMAIN.
WordPress.com copies the MX, subdomain, TXT, and SPF/DMARC records it can find into your account when you add the domain. Compare that copy with your old records and add any that are missing before you switch nameservers.
Frequently asked questions
Can I point a domain to WordPress hosting without moving the domain?
Yes. Pointing a domain only changes DNS, so the domain can stay with its current registrar. Change the nameservers or the A record at the registrar, and add the domain in your hosting panel. A transfer to the host is a separate step and is never required.
Why is my domain still showing the old site after I changed DNS?
DNS changes spread slowly. Old records stay cached until their TTL runs out, which can take up to 48 hours. Your own computer and browser may also cache the old answer. Test on a mobile connection or a fresh browser session, and wait a day before changing anything else.
Do I need to change nameservers to use WordPress?
No. You can keep DNS at your registrar and point only the A record at your host's server IP. Nameservers are simpler when the host will manage everything, but the A record route works just as well and keeps your email and other services where they are.
Will pointing my domain break my email?
It can, if you switch nameservers without copying your mail records. MX, SPF and DKIM records live in the DNS zone, so they stop working when the zone moves. Copy every record to the new zone first. The A record method leaves your existing DNS zone untouched, so email keeps working.
What is the difference between an A record and a CNAME?
An A record maps a domain name to an IP address, such as your host's server IP. A CNAME maps one name to another name, such as www to your root domain. Use an A record for the root domain and a CNAME for www, unless your host tells you otherwise.
Sources
- How to point a domain to Hostinger Hostinger Support
- How to Configure DNS Settings in WHM Bluehost
- Moving WordPress Developer.WordPress.org
- Moving WordPress WordPress Codex
- Connect a domain you registered elsewhere to WordPress.com WordPress.com Support
- Create DNS records Cloudflare Docs
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
