Nameservers are the part of the domain system that tells the internet where to find your website. When someone types your domain into a browser, nameservers are what direct that request to the right hosting server.
If you are moving to Bluehost, switching away from it, or connecting a domain registered elsewhere to your Bluehost hosting, changing nameservers is the step that makes it all work.
What Are Bluehost’s Nameservers?
Bluehost uses two nameservers for domains hosted on its platform:
| Nameserver | IP Address |
| ns1.bluehost.com | 162.88.60.37 |
| ns2.bluehost.com | 162.88.61.37 |
These are the values you need when pointing an externally registered domain to your Bluehost hosting account.
If your domain was registered through Bluehost, it is already pointed to these nameservers by default, and no action is required unless you want to change them.
When Would You Need to Change Nameservers?
There are three common situations where nameserver changes become necessary:
- You registered your domain with another registrar and want to host with Bluehost. Your domain is still pointing to the other registrar’s nameservers. Until you update them to Bluehost’s nameservers, your site will not load from your Bluehost hosting account.
- You are switching away from Bluehost to a different host. Your new hosting provider will give you their nameservers. You will update your domain’s nameservers, either through Bluehost’s portal if your domain is registered there, or through your registrar if you registered it elsewhere.
- You want to use a third-party DNS service. Some users point their domain to a third-party DNS provider such as Cloudflare to access advanced DNS features, DDoS protection, or performance improvements while keeping their hosting with Bluehost.
Before making any nameserver change, it is worth checking whether updating individual DNS records (A records or CNAMEs) would accomplish what you need without a full nameserver switch.
Changing nameservers hands full DNS control to the new provider, which can affect email, subdomains, and other services if those records are not correctly set up at the new provider before the switch.
How to Change Nameservers for a Domain Registered with Bluehost
If your domain is registered through Bluehost, you can manage its nameservers directly from the Bluehost Portal.
Step 1: Log in to your Bluehost Portal at bluehost.com.
Step 2: Click Domains in the left-hand menu. If you have one domain on the account, you will be taken directly to the domain management panel. If you have multiple domains, click the specific domain you want to manage.
Step 3: Select the Nameservers tab from the domain management panel.
Step 4: Click the Change Nameservers button.
Step 5: Enter the new nameserver values in the fields provided. If you are pointing to a new hosting provider, enter the nameservers they have given you. If you are setting up a third-party DNS service, enter the nameservers from that provider.
Step 6: Click Save to apply the changes.
DNS updates begin propagating as soon as you save, but it can take 24 to 48 hours for the change to be fully recognized across the internet. In some cases, updates are visible sooner, but allow the full window to pass before concluding that something has gone wrong.
How to Point a Domain Registered Elsewhere to Bluehost
If your domain is registered with another registrar, such as GoDaddy, Namecheap, or Network Solutions, you cannot change its nameservers from within Bluehost. You need to log in to that registrar’s control panel and update the nameservers there.
The general process is the same across most registrars:
Step 1: Find your Bluehost nameservers. Log in to your Bluehost Portal, click Hosting in the left-hand menu, and look for the Name Servers card. Use the Copy link to copy each nameserver value accurately.
Step 2: Log in to your domain registrar’s control panel.
Step 3: Navigate to the DNS or nameserver settings for your domain. The exact label varies by registrar but is typically found under Domain Management, DNS Settings, or Name Servers.
Step 4: Remove the current nameservers and replace them with Bluehost’s:
- ns1.bluehost.com
- ns2.bluehost.com
Alt: Entering Bluehost’s nameservers in Namecheap’s domain management panel under the Custom DNS setting.
Step 5: Save your changes. Allow up to 48 hours for propagation.
One important note: changing nameservers at your registrar will overwrite any custom DNS settings currently configured there.
If your domain uses custom DNS records to manage email, subdomains, newsletters, or other services, note those records before switching and confirm they are set up correctly at Bluehost before the propagation completes.
Understanding DNS Propagation
Propagation is the period during which your nameserver change spreads across DNS servers worldwide. It is not instant because DNS data is cached by servers and internet service providers, and each cache refreshes on its own schedule based on the TTL (Time to Live) value set by your previous DNS provider.
During propagation, some visitors may still see your old site while others see the new one, depending on which DNS servers their connection is using. This is normal and temporary. Avoid making further changes to your DNS settings during propagation, as additional updates can extend the process and make troubleshooting harder.
You can check whether your nameserver change is propagating correctly using online DNS lookup tools that test resolution from multiple global locations. If your Bluehost nameservers show as active in most regions, propagation is progressing correctly.
What to Do After Changing Nameservers
Once propagation is complete, work through the following to confirm everything is functioning correctly:
- Verify your website is loading. Visit your domain in a browser and confirm it is serving your site from your Bluehost hosting account.
- Test your email. If you use email addresses on your domain, send and receive a test message. A nameserver change can redirect email to a different server, and any misconfiguration in your MX records at the new DNS provider will cause delivery failures.
- Check your DNS records. Review the DNS records at your new provider to confirm that A records, CNAME records, and MX records are all correctly set up. If anything was missing in the transfer, add it manually.
- Back up your DNS settings. Save a record of your current DNS configuration so you have a reference point if you need to make adjustments or troubleshoot issues in the future.
- Monitor for the first 48 hours. Keep an eye on site availability and email delivery in the day or two following the change. If something is not working, it is far easier to diagnose and fix while the change is still fresh.
