Bluehost DNS Management Guide How to Edit, Add, and Troubleshoot DNS Records

Bluehost is one of the most popular shared hosting providers in the world, but its DNS management interface has changed significantly over the years, especially after the migration from cPanel to a custom dashboard. If you have just pointed a domain to Bluehost, need to add a Google Workspace MX record, or are troubleshooting why your site is not resolving, this guide walks you through every DNS task you are likely to encounter inside the Bluehost control panel, step by step.

How Bluehost DNS Works

Bluehost acts as both a web host and a domain registrar for many customers, which means your domain's nameservers and your DNS zone file can both live inside Bluehost. Understanding this distinction matters before you touch anything.

• Nameservers determine which DNS servers answer queries for your domain. Bluehost's default nameservers are ns1.bluehost.com and ns2.bluehost.com.
• DNS Zone File is the actual collection of records (A, CNAME, MX, TXT, etc.) that those nameservers serve.

If your domain is registered elsewhere (GoDaddy, Namecheap, Google Domains, etc.) but hosted on Bluehost, you have two paths: point the external domain's nameservers to Bluehost, or keep external nameservers and only copy individual records. Most users choose the first option. This guide covers both scenarios.

Accessing DNS Management in the Bluehost Dashboard

Bluehost rolled out its new custom dashboard starting in 2022, replacing the traditional cPanel for most accounts. The DNS zone editor is now in a different location than older tutorials show, which is a common source of confusion.

1. Log in at my.bluehost.com with your Bluehost credentials.
2. From the left sidebar, click Domains.
3. Click the domain you want to manage. If you have multiple domains, each has its own DNS zone.
4. Select the DNS tab near the top of the domain detail page.

You will now see a list of all DNS records currently set for that domain. Bluehost pre-populates several records automatically when your hosting account is created, including an A record pointing to your server's shared IP and a few cPanel-related CNAME records. Do not delete these unless you are sure what you are replacing them with.

Adding and Editing Common DNS Record Types

A Record (Root Domain and Subdomains)

An A record maps a hostname to an IPv4 address. The most critical A record is the one for your bare domain (often called the apex or root), typically shown as @ or your domain name with no subdomain prefix.

1. In the DNS tab, scroll to the A (Host) section and click Add Record.
2. In the Host field, enter @ for the root domain, or a subdomain name like shop for shop.yourdomain.com.
3. In the Points To field, enter the IPv4 address.
4. Leave TTL at 14400 (4 hours) unless you have a specific reason to change it. For planned migrations, set TTL to 300 (5 minutes) about 24 hours in advance.
5. Click Save.

CNAME Record (Subdomains and Service Verification)

CNAME records alias one hostname to another. They are commonly used for www, mail service verification, CDN subdomains, and third-party service integration like Shopify or HubSpot.

1. Scroll to the CNAME section and click Add Record.
2. In the Host field, enter the subdomain label only (e.g., www not www.yourdomain.com).
3. In the Points To field, enter the target hostname. Always include the trailing period if Bluehost accepts it, or confirm the full domain is saved correctly.
4. Click Save.

Important: You cannot create a CNAME record for your root domain (@). If a service like Shopify or Netlify tells you to point your root domain via CNAME, you must either use their IP address for an A record instead, or use a CNAME flattening solution — Bluehost's DNS does not natively support CNAME flattening.

MX Records (Email Routing)

MX records control where email for your domain is delivered. If you are switching from Bluehost email to Google Workspace, Microsoft 365, or Zoho Mail, you need to replace the existing MX records.

1. First, delete all existing MX records in the MX section. Bluehost default MX records point to its own mail servers. Leaving old MX records alongside new ones causes delivery failures.
2. Click Add Record in the MX section.
3. The Host field should be @ (root domain).
4. Enter the Points To value from your email provider (e.g., aspmx.l.google.com for Google Workspace).
5. Set the correct Priority number as specified by your provider. Lower numbers have higher priority. Google Workspace uses priority 1 for aspmx.l.google.com and priorities 5 and 10 for the fallback servers.
6. Repeat for each MX record your provider requires, then click Save after each entry.

TXT Records (SPF, DKIM, Domain Verification)

TXT records are used for email authentication (SPF and DKIM), domain ownership verification for services like Google Search Console, and security policies like DMARC. They are plain text strings with no special formatting, but the values must be entered exactly as provided.

1. Scroll to the TXT section and click Add Record.
2. In the Host field, enter @ for root-level records like SPF, or the exact subdomain label for DKIM (e.g., google._domainkey).
3. Paste the full TXT value into the TXT Value field. Do not add extra quotes — Bluehost adds them automatically.
4. Click Save.

A common mistake is adding a second SPF record when one already exists. SPF allows only one TXT record with a v=spf1 prefix per domain. If you need to add a new sending source, merge it into the existing SPF record rather than creating a new one.

Pointing an External Domain to Bluehost

If your domain is registered outside Bluehost, you need to update the nameservers at your registrar, not add records there. Log in to your external registrar (GoDaddy, Namecheap, etc.) and change the nameservers to:

After saving, DNS propagation can take anywhere from a few minutes to 48 hours depending on your registrar and the TTL on the previous nameserver records. Once propagation completes, all DNS management moves to the Bluehost DNS tab described above.

Alternatively, if you want to keep your domain's nameservers at the registrar and manage DNS there, you need to find out your Bluehost server's IP address (visible in the Bluehost dashboard under Hosting > cPanel > Server Information, or by pinging your temporary URL) and create A records at your registrar pointing to that IP.

Checking DNS Propagation After Changes

After saving a DNS record change in Bluehost, the record goes live on Bluehost's nameservers almost instantly — usually within 60 seconds. However, resolvers around the world cache old records until the TTL expires. This is why a record change that looks correct in your Bluehost dashboard may not yet be visible everywhere.

To check whether your changes have propagated globally, use the DNS Propagation Checker. Enter your domain name, select the record type you just changed, and see real-time results from dozens of DNS resolvers across multiple countries. If your own browser still shows the old record, try flushing your local DNS cache first.

Troubleshooting Common Bluehost DNS Problems

Site Not Loading After Nameserver Change

If you pointed an external domain to Bluehost nameservers but the site is not loading, check these in order:

• Confirm the nameserver change was saved at your registrar. Log back in and verify — some registrars require an email confirmation click before changes take effect.
• Use an authoritative DNS lookup to confirm Bluehost nameservers are actually answering for your domain: dig NS yourdomain.com @8.8.8.8
• Verify the A record inside Bluehost points to the correct shared hosting IP. Sometimes a domain is added to Bluehost but an A record was never created.
• Make sure the domain is added as an Addon Domain (legacy cPanel accounts) or a connected domain in the new dashboard under Domains > Add Domain. The DNS record alone is not enough — Bluehost's web server also needs to know that domain maps to your hosting account.

Email Stopped Working After DNS Changes

If email breaks after you edit DNS records, the most common causes are:

• Deleted the wrong MX record, or left a conflicting old MX record in place.
• SPF record was overwritten or duplicated, causing authentication failures.
• DKIM record has a typo in the hostname (the selector prefix like google._domainkey must be exact).

Run a quick check with dig to see what MX records are currently live:

CNAME Conflict Error When Saving

Bluehost will refuse to save a CNAME record if another record already exists for the same hostname. For example, if there is an A record for www, you cannot add a CNAME for www without deleting the A record first. This is standard DNS behavior, not a Bluehost bug. Delete the conflicting record before saving the CNAME.

Record Shows as Saved But Not Resolving

If a record appears in the Bluehost DNS tab but external queries still return nothing or an old value, check whether your domain is actually using Bluehost nameservers. If nameservers were changed recently, the old nameservers at your previous provider may still be authoritative during the transition window. Use dig NS yourdomain.com and confirm the output shows ns1.bluehost.com and ns2.bluehost.com before assuming Bluehost records are live.

Best Practices for Bluehost DNS Management

• Lower TTL before migrations: At least 24 hours before you plan to change your A or MX records, reduce TTL to 300. This makes propagation faster when the change happens.
• Restore TTL after migrations: Once everything is confirmed working, raise TTL back to 3600 or 14400 to reduce DNS query load and improve resolution speed for end users.
• Do not delete records you do not understand: Bluehost creates several internal records for cPanel functions, webmail, FTP, and autodiscover. Removing them unexpectedly can break services beyond just your website.
• Document every change: Keep a simple log with date, record type, old value, and new value. When something breaks three weeks later, this log is invaluable.
• Test from multiple locations: Your ISP's resolver might cache records aggressively. Always test from an external perspective using the propagation checker or dig with a public resolver like 8.8.8.8 or 1.1.1.1.

When to Use External DNS Instead of Bluehost

Bluehost's DNS is reliable for basic hosting setups, but there are scenarios where managing DNS through a dedicated provider like Cloudflare makes more sense. If you need CNAME flattening at the root, DDoS protection, sub-second TTLs, advanced traffic routing, or detailed query analytics, Cloudflare's free plan covers all of those. Migrating is straightforward: export your Bluehost DNS records, import them into Cloudflare, then update nameservers at your registrar to Cloudflare's assigned pair. Bluehost hosting continues to work normally — only DNS management moves.

For most small business and personal sites, however, Bluehost's built-in DNS management is sufficient. The key is knowing exactly where each setting lives and understanding what you are changing before saving. A five-minute mistake in a DNS zone can mean hours of downtime if you are not careful.