By David Russell · MentorsReview · Updated November 18, 2026
Affiliate disclosure. MentorsReview may earn a commission if you buy through our Bluehost or Namecheap links, at no extra cost to you.
Connect Namecheap domain to Bluehost
Keep the domain you own, connect it to the right WordPress site, and verify your website and email after the DNS change.
Compare Bluehost Hosting PlansAlready have hosting? Start setup
Keep your Namecheap domain. Choose hosting only if you still need it; compare the full first-term bill and renewal rate before checkout. Affiliate link.
Quick answer. Add your domain to Bluehost as an external domain and assign it to your WordPress site. Then follow the DNS instructions for that site. If Bluehost supports keeping your existing DNS provider for your plan, update the website records there. If Bluehost requires its nameservers, prepare a copy of the DNS records your email and other services need before switching. Your domain registration and renewals can stay with Namecheap.
What do you still need?
| Your starting point | Best next action |
|---|---|
| I own a Namecheap domain but need hosting | Compare Bluehost plans for your website count, storage and expected workload. View Bluehost Plans |
| I need a domain and hosting | Compare the separate domain and hosting totals before buying. Check Domain Availability |
| I already have both | No additional purchase is needed for this guide. Save your DNS records, then connect your existing domain. |
Bluehost hosts the website; Namecheap can remain your registrar. Compare any domain included with a hosting offer before paying separately for the same address. The links above are affiliate links.
Choose a DNS setup before you connect
Start by checking who actually hosts your DNS. In Namecheap, open Domain List, click Manage beside your domain and inspect the Nameservers setting. If your domain uses Namecheap BasicDNS, PremiumDNS or FreeDNS, look for editable host records under Advanced DNS. If it uses another provider’s nameservers, manage the records with that provider. Namecheap might still bill you for the registration while another provider controls the DNS. Namecheap’s guide to editing A records
| Your situation | Where to start | What to verify |
|---|---|---|
| New domain without email or subdomains | Follow the instructions in Bluehost Finish Setup | Root domain, www and HTTPS |
| Existing mailboxes and a supported record-based connection | Keep authoritative DNS and change the website records Bluehost specifies | Mail records, web targets and both hostnames |
| Bluehost requires a nameserver change | Prepare the destination DNS zone before changing delegation | MX, mail authentication, subdomains, verification and DNSSEC status |
| Existing live site moving to Bluehost | Copy and test the website before changing DNS | Content, forms, certificate, redirects and rollback |
An A record points a hostname to an IPv4 address. A CNAME points one hostname to another hostname. Nameservers decide which DNS provider answers questions about the whole domain. A nameserver change can affect the records used by email, subdomains and third-party services. If you are still comparing how much control and work each setup requires, see our GoDaddy vs Bluehost vs Namecheap comparison.
Make a record of the current setup
Save the current nameservers and the DNS records for the root domain, www, mail and any other active subdomains. For each record, capture its type, host, value, TTL and MX priority where applicable. Mail setups often include MX records for delivery, a TXT record for SPF, TXT or CNAME records for DKIM, and a TXT record for DMARC. You may also have ownership verification records for Search Console, a mailing service or a workplace platform.
If you are migrating an existing WordPress site, confirm that you have a usable backup of the database and files. Test the new copy as far as your temporary URL or your host’s preview permits. If the site takes orders or user registrations, plan when to copy the latest data and how you will prevent new writes from going to the old copy during the switch. Record who can access both hosting accounts and the DNS dashboard so the person handling a rollback has everything they need.
- Save the current nameservers and all records needed by active services.
- Confirm the destination WordPress site and the exact DNS targets in Bluehost.
- Prepare email records at the destination if you will change nameservers.
- Keep a tested backup and the previous DNS values available for rollback.
Buy the plan your site needs
If Bluehost is your intended destination and you have not purchased hosting yet, compare the available plans before changing DNS. Match the plan to the number of sites you will run and the resources your project needs.
- Check the full amount due today. Compare equivalent billing terms, taxes and optional extras rather than only the advertised monthly figure.
- Read the renewal amount. Add your domain renewal and any paid email, backup or security services to your ongoing budget.
- Confirm the essentials. Check website limits, storage, SSL terms, migration assistance and backup coverage for the exact plan in your cart.
- Review cancellation terms. Read the current refund conditions and any exclusions for domain registration or other services before payment.
Check Bluehost Plans & Current Pricing
Affiliate link · Pricing and inclusions can change. Confirm the current checkout terms. Already a Bluehost customer? Continue with your existing account below.
How to connect Namecheap domain to Bluehost
- In the Bluehost portal, open Domains, choose Add a Domain and select Connect an external domain. Enter your bare domain, without https or www.
- Open the newly added domain. Under Connections, use the Website card to connect it to the intended hosting plan.
- For an existing WordPress installation, open Websites, click Manage on the correct site and use its Domains tab to add the external domain. If you are starting a fresh site, use the workflow for a new WordPress installation.
- Find the connected domain and open Finish Setup. Record the exact DNS targets and verification instructions shown for that site. A connection displayed in the Bluehost dashboard is one checkpoint. Public routing and HTTPS are separate checks.
On accounts that host multiple WordPress sites, compare the site name and temporary URL before completing the assignment. DNS can point to the correct hosting provider while the hosting account routes the request to the wrong website. If your account only shows nameserver instructions and you want to retain another DNS provider, confirm whether Bluehost supports record-based pointing and certificate validation for your specific plan before editing anything. Bluehost’s external domain setup guide
Option 1. Keep your DNS provider and update website records
Use this option if Bluehost supplies and supports the web targets for your setup. Open the dashboard for the authoritative DNS provider. On eligible Namecheap DNS plans, go to Domain List → Manage → Advanced DNS → Host Records. Change the records for the root and www to match Bluehost’s instructions. In Namecheap, the host value @ represents the root domain. The www host represents the www version.
If Bluehost specifies an IPv4 address for the root, enter that as the value of the A record. If it supplies a hostname as a CNAME target for www, enter that hostname where the DNS provider requests the destination. Use the values assigned to your site. A hostname copied from an old tutorial, a control-panel login address or an IP associated with somebody else’s plan can send traffic to the wrong server.
Review what already exists for each web hostname. A parked domain can have a redirect or a parking record that needs replacing. A domain that previously had IPv6 can still have an AAAA record sending some visitors to the old server. Ask your new provider whether it supplies an IPv6 target before deciding what to do with that old record. Keep unrelated mail, verification and subdomain records in place. If your email uses a hostname whose address depends on the root domain, confirm the dependency with the email provider before editing the root.
A website moves while company email stays put
Suppose the root domain and www are used by a small WordPress site. Google Workspace handles its mail, and a newsletter provider uses a separate verification record. With a supported web-record connection, you would review and change the web targets Bluehost specifies, then keep using the existing mail and newsletter records. After the change, visit both web addresses and send mail in both directions from an outside mailbox. This verifies the two services independently.
Option 2. Point the domain to Bluehost nameservers
Use this route if your Bluehost setup requires its nameservers or you want Bluehost to host the entire DNS zone. The Bluehost help guide lists default nameservers, but confirm the values displayed for your account. First check whether the destination DNS zone can be edited before the switch. Recreate the records required by your mail, subdomains and verification services there. If you cannot prepare the zone in advance, coordinate the cutover with Bluehost support and choose a window that gives you time to verify and correct the zone.
At Namecheap, open Domain List → Manage, find Nameservers, choose the custom setting and enter the values from Bluehost. Save the change. Then use the DNS dashboard for the nameservers that are now authoritative. Editing the old Namecheap host-record screen after delegation moves will not update the records the new DNS provider serves.
If your domain uses DNSSEC, review the migration procedure with both DNS providers before switching. A mismatch between signing at the DNS provider and the DS record published through the registrar can prevent validating resolvers from answering. Record your previous nameservers and keep the former zone available during a planned migration if the old provider allows it.

Verify your site and email after the change
Start with DNS, then work up to the application. You can look up the current NS and web records with a DNS lookup tool. Compare the answers with your saved targets. Try both the root and www over HTTPS. One version should be your preferred public URL and the other should redirect there once both hostnames are configured and covered by HTTPS. Confirm the preferred address loads an actual page from your WordPress site.
Test at least one internal page and one action that matters, such as the contact form or a product checkout in test mode. Watch for images or links pointing to the temporary domain. Review the WordPress Site Address and Home URL if you migrated from a temporary hostname. Use the host’s migration tooling where available so changes to stored WordPress data preserve its format. For an existing website, sample important old URLs and confirm their destinations and status codes.
For email, send a message from an unrelated address to your domain and reply from the domain mailbox. Check forwarding and form notifications if you rely on them. A single successful homepage load tells you whether that browser reached your site at that moment. It says little about whether recipients can reach you by email.
Troubleshooting connection problems
I still see a parking page or the old site
Compare the current A, AAAA and CNAME answers with your planned values and check whether you edited the authoritative DNS zone. Also confirm that the domain was assigned to the intended WordPress site in Bluehost. A cache can account for different results across networks, but an incorrect authoritative answer needs correction.
The root loads, but www fails
Check for a missing or conflicting www record. Then confirm Bluehost recognizes that hostname and that the certificate covers it. If www is your secondary address, retry the redirect after HTTPS works for both names.
The website loads with a certificate error
Check the exact hostname where the error appears, whether DNS resolves to the expected destination and whether the host shows the certificate as pending or active. If the domain previously used a CDN or had restrictive CAA records, share that information with support if issuance stalls.
Email stopped after switching nameservers
Compare the authoritative zone with the old record list. Start with MX, then review the records and hostname dependencies documented by the mail provider. If a missing record is the cause, restore the required value at the current authoritative provider and retest incoming and outgoing mail.
I need to roll back
Restore the previously recorded web targets or nameservers that match the change you made. For a site with new orders or account activity, identify which copy has the latest data before sending visitors back. DNS caching can keep some users on each destination for a time. Keep both copies accessible to your team while you verify the rollback.
Frequently asked questions
Do I have to transfer my domain from Namecheap to Bluehost?
You can keep the registration, billing and renewal with Namecheap while connecting the website to Bluehost. A transfer is a separate change to which registrar manages your domain. If you later transfer, review the renewal terms and lock status before starting. See our Namecheap renewal pricing guide.
How long does it take to connect the domain?
The website may begin resolving once the new records appear in DNS, and some networks can retain older answers until cached records expire. Nameserver changes also involve delegation. Track DNS answers, certificate status and website behavior as separate milestones instead of assuming every visitor sees the same result after a fixed number of hours.
Should I buy another domain from Bluehost if I already have one?
Use the Namecheap domain you already own if it is the address you want customers to remember. If you are weighing a Bluehost offer for a second domain, check term eligibility and renewal costs. Our Bluehost free domain guide covers the questions to ask before accepting a bundle.
Can I replace my old hosting as soon as the homepage loads?
Keep the existing hosting available until you have verified HTTPS, important pages, forms, email and any business-critical workflows. If the old host also runs your mailboxes or another website, check those dependencies before cancelling. Save a final backup and document where each service now lives.
Your domain. Your hosting. A clear launch plan.
Already own your Namecheap domain? Keep it and choose a Bluehost hosting plan only if you still need hosting. Have both accounts ready? Return to the connection steps and verify your website, HTTPS and email before retiring an old service.
Compare Bluehost Hosting PlansFind a Namecheap Domain
Affiliate links · Compare registration and renewal costs, plan terms and optional add-ons before purchasing.
Start the connection steps · Verify your finished setup · Read our Namecheap offers guide






