A custom domain can make a Blogger site easier to remember and give it a consistent address for readers. But connecting the domain is more than typing a URL into Blogger. You must configure DNS records, verify ownership, and check that HTTPS and redirects work correctly.
This step-by-step guide explains how to connect a domain such as www.example.com or blog.example.com to Blogger, what the two CNAME records do, when the four optional A records matter, and how to fix common errors. You do not need to move your existing blog posts to a new platform.
If you are still comparing platforms and their limitations before choosing a permanent address, our guide to blogging tools and platforms can help you decide whether Blogger fits your site. The DNS steps below are specifically for Blogger.
Before you connect a custom domain
You need three things:
- An existing Blogger blog that you can access as an administrator.
- A domain you control, purchased through a domain registrar or another provider.
- Access to the domain's DNS settings, usually a section called DNS Management, DNS Zone, or Advanced DNS.
Decide which subdomain will be your main blog address. Common choices are www.example.com and blog.example.com. Blogger's supported custom-domain setup uses a subdomain. If you want visitors who type example.com without www to reach your blog, configure the separate root-domain redirect later in this tutorial.
Important: If your domain already serves another website, email, or online store, changing DNS records may affect those services. Export or record the current DNS configuration before making changes. Do not remove MX, TXT, or unrelated DNS entries just to connect Blogger.
Step 1: Enter the custom domain in Blogger
- Sign in to Blogger and choose the correct blog.
- Open Settings and scroll to Publishing.
- Select Custom domain.
- Enter the complete subdomain, for example
www.example.com, without a path such as/blog. - Click Save.
On the first attempt, Blogger often displays an error with two CNAME records. That can be an expected verification step, not a sign that your domain cannot work. Keep the message visible or record its values accurately.
The official Blogger custom-domain instructions explain the CNAME values and the DNS verification process.
Step 2: Create the two CNAME records
Sign in to your domain or DNS provider. Open the DNS management page for the exact domain you are connecting. You normally need two distinct CNAME records.
CNAME 1: Send the blog subdomain to Blogger
If your blog address will be www.example.com, configure this record:
- Type: CNAME
- Name/Host:
www - Target/Points to:
ghs.google.com
If your address will be blog.example.com, use blog as the host instead of www. DNS dashboards vary: one provider may want only www, while another may show or automatically append the main domain. Check the completed hostname before saving so you do not accidentally create www.example.com.example.com.
CNAME 2: Verify ownership of your blog and domain
Blogger provides another CNAME with a unique host and destination specific to your blog and Google Account. Copy both values exactly from the message in Blogger. They are not universal values, so do not copy verification tokens from a screenshot or another website.
An example destination may end in .dv.googlehosted.com, but the beginning of the address varies. The correct value is the one Blogger shows for your account.
If your DNS provider reports that a host name already has a conflicting record, inspect that record before editing it. A CNAME typically cannot coexist with another record type at the same host name. Make only the change needed for the intended blog subdomain.
Step 3: Wait for DNS and save the domain again
DNS updates are not always immediate. Blogger recommends waiting at least an hour before repeating the custom-domain save. Depending on the DNS provider and cached records, propagation can take longer; Google's related CNAME documentation notes that changes may take up to 48 hours.
- Wait after saving the DNS records.
- Go back to Blogger → Settings → Publishing → Custom domain.
- Enter the same subdomain and click Save again.
- If verification still fails, compare the two displayed CNAMEs against the DNS entries character by character.
A DNS lookup tool can help you inspect whether the public CNAMEs are visible, but remember that different locations may see changes at different times. Avoid repeatedly replacing records when they are already correct.
Step 4: Redirect the root domain to the blog (optional)
If you want a visitor typing example.com to reach www.example.com, Blogger provides a separate Redirect domain setting. This is different from the first CNAME, which connects the www or blog subdomain.
For the root domain, Google's Blogger instructions list these four IPv4 A-record destinations:
216.239.32.21216.239.34.21216.239.36.21216.239.38.21
They normally use @ or the provider's equivalent blank/root host. These records are intended for the root-domain redirect, not for the www CNAME. If the root domain currently points to another active website, changing its A records will redirect or disrupt that service; decide which service should own the root address before proceeding.
Once the DNS is configured, turn on Redirect domain under Blogger's Publishing settings when the option is available for your connected domain. Then test both the root and www versions.
Step 5: Enable HTTPS and check the secure address
Open Settings → HTTPS and inspect the availability and redirect settings for your custom domain. After Blogger provisions HTTPS for the domain, enable the redirect to send readers from HTTP to HTTPS where supported.
A newly connected domain may need additional time before HTTPS becomes available. If your DNS zone uses CAA records to restrict which certificate authorities can issue certificates, Blogger's official documentation specifically says your policy must allow letsencrypt.org for Blogger to issue or renew the SSL certificate.
Read Google's Blogger HTTPS help if the secure version is unavailable or fails to redirect. Do not publish login forms or collect sensitive data on a page with a broken certificate.
Step 6: Verify your links and search settings
After connecting the domain, check the site as a visitor:
- Open the custom-domain home page with
https://. - Open a few older blog posts and static pages; they should display on the new domain.
- Test the old
blogspot.comaddress and note whether Blogger redirects it as expected. The change may take time. - Check links in the menu, footer, and social profiles for unnecessary redirects or outdated hard-coded addresses.
- Inspect Google Search Console for the relevant property and add or verify the domain if necessary. A domain change may temporarily affect search reporting while Google processes the new URLs.
If your theme or post code loads images, scripts, or other embedded resources over http://, switch to their HTTPS addresses where available and check for mixed-content warnings. A plain link that opens another page is not an embedded resource. Do not blindly rewrite every URL inside a theme without keeping a backup.
Troubleshooting common Blogger domain errors
“We have not been able to verify your authority to this domain”
Check both CNAME records, not just the one pointing to ghs.google.com. The second record must use the exact security host and destination supplied for your blog. Check the host-name field for duplicated domain names and allow DNS time to propagate.
The www address works, but the root domain does not
A working www CNAME does not automatically configure example.com. Review the four root A records and Blogger's Redirect domain switch. If a separate website owns the root domain, leave its DNS intact and use the blog subdomain by itself.
The domain works over HTTP but HTTPS is unavailable
Give Blogger time to issue the certificate, confirm that the custom domain is saved and DNS points to Blogger, and examine any restrictive CAA records. Check the official HTTPS guidance before changing unrelated settings.
The domain shows a different website or a redirect loop
Look for conflicting DNS records, URL forwarding rules at the registrar, or a proxy/CDN service that is applying its own redirect. Avoid having multiple services try to redirect the same hostname in different directions. If the browser reports too many redirects, follow our Blogger custom-domain redirect loop checklist.
Old posts are missing after the change
Do not delete or recreate the posts. The custom domain should change the blog address, not erase content. Check the individual post URL, any custom redirects you created, and whether you selected the correct Blogger blog.
Frequently asked questions
Do I need web hosting to use a custom domain with Blogger?
No separate web-hosting subscription is required to keep the blog on Blogger. You do need the domain itself and access to its DNS settings.
Can I connect the root domain directly to Blogger without www?
Blogger's standard custom-domain connection uses a subdomain such as www or blog. You can typically configure the root domain to redirect to that address using Google's documented A records and Blogger's redirect option.
Why does Blogger ask for two CNAME records?
One connects your chosen subdomain to Blogger. The other verifies your authority to use the domain and is specific to your blog and Google Account.
How long does Blogger custom-domain setup take?
Some changes work after an hour, but DNS propagation and redirect or HTTPS activation may take longer. Give the records time to update before repeatedly editing a correct configuration.
Will connecting a custom domain delete my Blogger posts?
No. Connecting the domain changes the blog's public address; the existing posts and pages remain in your Blogger account. However, check internal links, navigation, and search reporting after the switch.
Final setup checklist
Confirm that the two CNAME records are correct, Blogger has saved the subdomain, the optional root redirect does what you want, HTTPS works, and old posts still open. Keep a copy of your DNS settings and refer to the official setup guide whenever Blogger changes its interface or requirements.

