
When you build a site on Bluehost, it often starts on a temporary domain. To go live under your own name, you have to point the domain you already own at Bluehost. This Seahawk Learn video walks through the whole process for a domain registered at Namecheap, from the Bluehost dashboard to a live site on your custom domain.
The steps below follow the video and explain what is happening behind each one, so the same process makes sense with any other registrar.
How domain connection works
A domain name is a label that has to point to a server. Your registrar (where you bought the name) stores the domain, while your host (here Bluehost) stores the website files. Connecting the two means telling the internet where to look. There are two common ways to do it:
- Change the nameservers. You replace the registrar's nameservers with Bluehost's, so Bluehost manages the domain's DNS records. This is the method shown in the video.
- Change individual DNS records. You keep DNS at the registrar and edit the A record that points to your Bluehost server. This is useful if you also run email or other services through the registrar's DNS.
If you want more background on records and how they work, see our easy guide to WordPress DNS setup.
Before you start
- Make sure you can log in to both your registrar account and your Bluehost account.
- Note any email service tied to the domain. Changing nameservers can affect email records, so write down existing MX records first.
- If the domain already has a live site elsewhere, plan the change carefully. Your visitors will move to the new host once DNS updates.
Step-by-step: connect your domain to Bluehost
- Open the Bluehost dashboard. Find the domains section and look at the connection options. The video starts with a quick tour so you know where to look.
- Choose to connect an external domain. Select the option for a domain registered elsewhere and enter your domain name. Bluehost will show you the nameservers to use.
- Copy the Bluehost nameservers. You will usually be given two. Copy them exactly as displayed.
- Update the nameservers at your registrar. In the video this is done in Namecheap. Open the domain's settings and change the nameserver option from the default to custom DNS, then paste in the two Bluehost values and save.
- Wait for DNS propagation. The change spreads across the internet's DNS servers over time. It is sometimes fast and sometimes takes many hours, so be patient.
- Connect the domain to your website. Back in Bluehost, assign the domain to your WordPress site so it replaces the temporary domain.
- Check that it works. Visit your domain in a private browser window. The video ends with the site live on the custom domain.
What DNS propagation means
DNS records are cached by internet providers and devices to keep browsing fast. After you change nameservers, those caches take time to refresh. During this window some visitors may see the old site while others see the new one. This is normal, not an error. You cannot force it to finish, but you can check progress from a different network or with an online DNS lookup tool. Avoid changing settings repeatedly while you wait, as that only makes troubleshooting harder.
SSL and the WordPress site address
Once the domain points at Bluehost, your site needs an SSL certificate so it loads over HTTPS. Hosts typically provision one automatically after the domain connects, but it may take a little while. If the browser shows a security warning at first, wait and test again before changing anything. Our guide to getting free SSL for WordPress covers what to do if it does not appear.
Then check Settings, General in WordPress. The WordPress Address and Site Address should both use your new domain with https. If they still show the temporary domain, update them and save.
Common problems
- The old site still appears. Propagation is not finished. Test again later and clear your browser cache.
- Your email stopped working. Nameserver changes replace the DNS zone. Recreate your MX and other email records in the new DNS zone.
- The domain will not connect inside Bluehost. Check that you used the exact nameserver values and that the domain is not locked or pending a transfer at the registrar.
- A security warning appears. The certificate has not been issued yet. Wait and try again.
Connecting versus transferring
Connecting a domain does not move its registration. You still renew it at Namecheap or wherever you bought it. If you would rather manage the domain and hosting in one place, you can transfer the domain, which is a separate process. Our guide on how to transfer a domain explains it. Choosing the right name in the first place also matters, and our tips for choosing the perfect WordPress domain name help with that.
What the video covers
- 0:00 Introduction
- 1:18 Bluehost dashboard walkthrough
- 2:10 Domain connection options
- 3:09 Connecting an external domain
- 4:30 Updating nameservers in Namecheap
- 5:20 DNS propagation explained
- 6:31 Connecting the domain to your website
- 7:55 Connecting your Namecheap account
- 9:21 Website live on the custom domain
- 9:39 Final thoughts
Ready to go live on your own domain?
The process is short: point the nameservers, wait for propagation, assign the domain to your site and confirm HTTPS. Do it at a quiet time, keep a note of your email records, and test in a private window. You can read more about hosting plans on the Bluehost website.
FAQs
How long does it take for a domain to connect to Bluehost?
The settings take effect as soon as you save them, but DNS propagation can take anywhere from a few minutes to many hours before every visitor sees the new site.
Do I need to move my domain registration to Bluehost?
No. You can keep the domain registered at Namecheap or another registrar and connect it by changing nameservers or DNS records. Transferring is optional.
Will changing nameservers break my email?
It can. Nameservers control the DNS zone, so any MX and other email records must exist in the new zone. Record them before you switch and recreate them afterwards.
Why does my site show a security warning after connecting?
The SSL certificate may not have been issued yet. Wait a while, test again, and then check the certificate status in your hosting dashboard.
