How to Add Domain to Bluehost?

Adding a domain to your Bluehost account takes about five minutes and follows the same process whether your domain is registered with Namecheap, GoDaddy, Google Domains, IONOS, Porkbun, Cloudflare Registrar, or any other registrar. If you registered your domain directly through Bluehost, it should already be attached. You can skip to Step 4 to confirm it is assigned correctly.

This guide covers the registrar side of the process: updating the nameservers or A record at wherever you bought your domain, so the domain points to Bluehost. If you want to manage domains already connected to your Bluehost account, see our guide on how to assign a domain to Bluehost. For the bigger picture (nameservers, DNS records, email DNS), the Bluehost domain and DNS guide ties everything together.

What Needs to Happen to Add a Domain to Bluehost

For your domain to work on Bluehost, it needs to point to Bluehost’s servers. This is done in one of two ways:

• Nameservers (recommended): update the nameservers at your domain registrar to ns1.bluehost.com and ns2.bluehost.com. This hands full DNS control to Bluehost.
• A Record: point the domain’s A record to Bluehost’s IP address (shown in your Bluehost control panel under Domains). Use this if you want to keep DNS management at your registrar.

Either change should be made before you assign the domain inside Bluehost, so both steps complete together and the domain goes live faster.

Will Adding a Domain Affect My Email?

This is the question most guides skip, and it is the most common cause of problems.

If you switch your domain’s nameservers to Bluehost, you are moving full DNS control to Bluehost. This includes your MX records, which control where your email is delivered. The result depends on whether your email is hosted with Bluehost or somewhere else:

• Email hosted at Bluehost: No problem. Bluehost automatically sets up the MX records for their own email service when you assign the domain.
• Email hosted at Google Workspace, Microsoft 365, Zoho, or another provider: You must manually re-add your MX, SPF, DKIM, and DMARC records inside Bluehost’s DNS panel after switching nameservers. If you do not, email delivery stops.
• Using the A Record method instead of nameservers: Your DNS stays at your registrar, so existing MX records are untouched. Email is not affected.

If you are on a third-party email provider, write down your current MX records before changing nameservers. Log into Bluehost after the switch and re-add them under Domains > DNS.

Updating Nameservers at Major Registrars

Where you find the nameserver settings depends on which registrar holds your domain:

• GoDaddy: Log in, go to My Products, click DNS next to your domain, then scroll to Nameservers and select Change.
• Namecheap: Log in, go to Domain List, click Manage next to your domain, then open the Nameservers section and switch to Custom DNS.
• Google Domains (now Squarespace Domains): Log in, select your domain, go to DNS, then choose Custom Name Servers and enter the Bluehost nameservers.
• IONOS: Log in, go to Domains & SSL, click the three-dot menu next to your domain, choose DNS, then find the Nameservers tab and switch to Custom.
• Porkbun: Log in, find your domain in the dashboard, click Details, then scroll to Authoritative Nameservers and click Edit to enter custom nameservers.
• Cloudflare Registrar: Log in to the Cloudflare dashboard, go to the Registrar section, select your domain, then choose Configuration and update the nameservers. Note: switching nameservers away from Cloudflare disables Cloudflare’s proxy protection. If you want to keep Cloudflare in front of Bluehost for performance or DDoS protection, use the A record method instead and keep your nameservers at Cloudflare.

Three Things That Go Wrong When You Add a Domain to Bluehost

These are the three failure modes that support tickets and forum posts repeat most often. Each has a specific fix that takes under two minutes once you know where to look.

1. Domain Shows the Bluehost Parking Page After 48 Hours

This means your registrar pointed the domain at Bluehost correctly, but Bluehost received it as a parked domain rather than assigning it to your WordPress site. The domain resolved to Bluehost’s servers, Bluehost found no assignment, and served its default parking page. Fix: log into Bluehost, go to Domains, find the domain in your list, click the three-dot menu next to it, and look for “Assign” or “Edit Assignment.” Change the “Assigned Site” dropdown from None to your WordPress site. The parking page disappears within a few minutes once the assignment saves.

2. SSL Certificate Missing After the Domain Points Correctly

Bluehost auto-provisions a free SSL certificate, but the trigger fires only when the domain status is set to Assigned. Parked domains and Add-On domains that have not been assigned to a site do not receive automatic SSL. If your domain resolves to your WordPress site but shows “Not Secure” in the browser, go to Bluehost > Security > SSL/TLS and click “Install Certificate” for the domain. If the install button is greyed out or returns an error, the domain status in the Domains panel is likely still Parked; fix the assignment first, then retry the SSL install.

3. Email Stops Delivering After the Nameserver Switch

When you move nameservers to Bluehost, Bluehost creates default MX records pointing at its own mail servers. If your email was running through Google Workspace, Microsoft 365, or any external provider, those custom MX records no longer exist in DNS. Outgoing mail from your domain will still work for a short window (the old records are cached), but incoming mail will begin failing as the cache expires, usually within 24 to 48 hours. Fix: log into Bluehost > Domains > DNS Management, delete Bluehost’s default MX records, and add your email provider’s MX records manually. Google Workspace MX records are documented in Google’s admin console under Apps > Google Workspace > Gmail > Set up MX records.

Step-by-Step: Adding the Domain Inside Bluehost

Step 1: Log Into Bluehost

Go to bluehost.com and log in with your account email and password. You land in the BlueRock dashboard. If your account still uses Legacy cPanel, the path is slightly different and noted at each step below.

Step 2: Go to the Domains Panel

In BlueRock: click Domains in the left sidebar. In Legacy cPanel: scroll to the Domains section and click Addon Domains.

Step 3: Add the Domain

In BlueRock: click Add Domain and enter the domain name without www. Choose whether to add it as an Addon domain (its own site) or a parked/alias domain (a mirror of an existing site). For a new WordPress site, choose Addon. In Legacy cPanel: enter the domain in the “New Domain Name” field; cPanel auto-fills the subdomain and document root fields, which you can leave as-is.

Step 4: Assign the Domain to Your Site

After adding the domain, return to the Domains list. Find the domain and confirm its Assigned Site shows your WordPress install. If it shows “None” or “Parked,” click the three-dot menu and assign it manually. This is the step most guides skip, and it is the direct cause of the parking page problem described above.

Step 5: Update Nameservers at Your Registrar

Log into your registrar and update the nameservers to ns1.bluehost.com and ns2.bluehost.com. If you are using the A record method instead, find your Bluehost server IP under Bluehost > Hosting > Server Information, then create an A record pointing your domain and a CNAME pointing www to your domain root.

Step 6: Wait for Propagation and Verify

DNS propagation takes anywhere from a few minutes to 48 hours depending on your registrar and the TTL on your old records. Once the majority of global DNS servers resolve correctly, your site will load and SSL will auto-provision within the hour.

Adding a Subdomain Instead of a Full Domain

If you want to point a subdomain (for example, shop.yourdomain.com) at Bluehost rather than the root domain, the process skips the nameserver change entirely. Create a CNAME record at your registrar pointing the subdomain to your Bluehost account’s hostname (found under Hosting > Server Information). Then add the subdomain inside Bluehost under Domains > Subdomains. Bluehost will provision SSL for the subdomain the same way it does for root domains, provided the CNAME resolves correctly before you trigger the certificate.

Remember: use ns1.bluehost.com and ns2.bluehost.com, allow up to 48 hours for DNS to propagate, check that the domain is set to Assigned (not Parked or Unassigned) if the site does not load, and re-add your MX records inside Bluehost if you use a third-party email service. Not yet a Bluehost customer? Sign up for Bluehost here before following this guide. If you are adding a domain as part of setting up WordPress, our guide on how to install WordPress on Bluehost covers the next step. If you need to change nameservers (for example, to point an externally registered domain to Bluehost or to move hosting away from Bluehost), see our step-by-step guide on how to change nameservers on Bluehost.