
A working www address does not automatically redirect the bare domain in Blogger. Blogger hosts a custom blog address with a subdomain such as www.example.com, while example.com needs its own redirect setup. Google’s documented method uses four A records at the domain provider and Blogger’s Redirect domain setting.
If www.example.com opens your blog but visitors who enter example.com see an error, an old page, or no site at all, check those two parts separately. The existing CNAME for www proves only that the www host has been connected. It does not finish the root-domain redirect.
Why the www address can work on its own
A domain name has separate hostnames. www.example.com and example.com look closely related to a visitor, yet DNS and Blogger treat them as different addresses.
Blogger’s settings documentation says that blogs cannot be hosted at naked domains such as example.com. A Blogger custom domain must include www or another subdomain, such as blog.example.com. The same documentation describes Redirect domain as the setting that redirects the naked domain to the custom domain.
That distinction explains the common result: www.example.com loads correctly, but typing example.com does not reach the blog. The blog’s custom-domain connection may already be valid. The redirect path remains unfinished.
Google’s setup instructions use www.mydomain.com as the destination for readers who enter mydomain.com. Your own preferred subdomain may differ, provided it is the custom domain already connected to the blog. If your blog uses blog.example.com, the root redirect should lead to that address rather than silently changing the blog to www.example.com.
Keep this issue separate from two other Blogger tasks:
- The CNAME records connect the selected subdomain to Blogger and verify the blog.
- HTTPS controls secure delivery for a custom domain.
- The root redirect sends visitors from the bare domain to the existing custom domain.
Those settings can affect the same site, yet each one solves a different part of the setup.
Confirm the custom domain already configured in Blogger
Before changing DNS, open Blogger and identify the custom address shown under Settings and Publishing. Use that exact address as the redirect destination. A custom domain can be www.example.com, but Blogger also accepts another available subdomain.
Google’s custom-domain guide says to enter the domain URL in Blogger, save it, then use the two CNAME values shown in the error message if Blogger requests them. One CNAME points the chosen subdomain, such as www, to ghs.google.com. The other is a security CNAME generated for the individual blog and Google Account.
The root redirect does not replace those CNAME records. Leave a working www CNAME in place while you address the bare domain.
Google also says that a Blogspot address can take up to 24 hours to redirect to a custom domain. That timing concerns the separate Blogspot-to-custom-domain change. It does not prove that the bare domain is configured, and it does not promise that a newly changed root redirect will work immediately.
Add Blogger’s documented A records for the bare domain
Google instructs Blogger users to add four A records for a naked redirect. Enter them in the DNS area of the domain provider that manages your domain.
| Record type | Host or name | Value |
|---|---|---|
| A | @ or the provider’s root-domain field |
216.239.32.21 |
| A | @ or the provider’s root-domain field |
216.239.34.21 |
| A | @ or the provider’s root-domain field |
216.239.36.21 |
| A | @ or the provider’s root-domain field |
216.239.38.21 |
The label for the bare domain varies by provider. Some dashboards use @; others leave the host field empty or display the registered domain automatically. Follow the provider’s own field labels while entering the four IP addresses from Google’s instructions.
Check existing root A records before removing or replacing anything. Google’s guidance says that existing A records for the bare domain should be removed when setting up this redirect. Those records may currently send the bare domain to another website, hosting account, email-related service, or a parked page. Reviewing what they serve first helps you avoid an accidental change whose effect you did not expect.
Do not add these four A records to the www host. The CNAME for the chosen subdomain and the A records for the bare domain have separate jobs. Mixing them can leave the domain in a confusing state.
Avoid treating this list as a general DNS recipe for every website. These are the A records documented by Google for Blogger’s naked-domain redirect procedure. A domain used with another platform may require a different setup.
Turn on Redirect domain in Blogger
DNS records alone do not complete the Blogger configuration. Google’s instructions say to return to Blogger after adding the A records and enable the redirect setting.
Open the relevant blog, then go to Settings. Under Publishing, turn on Redirect domain (mydomain.com to www.mydomain.com). Blogger describes this option as one redirect from the naked domain to the custom domain.
Use the setting after the custom domain itself has been saved and connected. If the listed custom domain is www.example.com, the option should send example.com to www.example.com. If you selected another subdomain, Blogger should redirect the bare domain to that selected custom address.
This toggle matters because Blogger does not host the blog directly at the bare domain. It directs traffic onward to the custom domain that Blogger supports.
The setting is easy to miss because it appears close to the custom-domain field. A site owner may focus on the successful www address, then assume the root domain will follow. It needs its own DNS records and its own Blogger setting.
Check the result without guessing
DNS changes need time to activate. Google’s setup guide says to wait at least one hour after entering DNS settings before repeating the Blogger custom-domain setup. A provider may also have its own propagation window. Repeatedly changing records during that period makes troubleshooting harder, since you no longer know which configuration is being tested.
After waiting, check both addresses separately:
- Open the exact custom domain, such as
www.example.com. - Open the bare domain, such as
example.com. - Confirm that the bare domain ends at the custom domain.
- Check that the final address is the one saved under Blogger’s Publishing settings.
A successful www test only confirms the custom-domain side. A successful root test confirms the redirect path as well. Test both forms because visitors may use either one.
If the root domain still fails, first compare the records at the domain provider with Google’s four documented IP addresses. Then check that Redirect domain is enabled in Blogger. Look for extra A records on the root host, typographical errors, or records entered on www instead of the root domain.
The provider’s DNS interface can name fields differently, but the record values still need to match Google’s instructions. A CNAME record for www does not substitute for the four root A records. A record that points to an old server can also keep the bare domain from reaching Blogger’s redirect.
When the domain provider needs to help
Contact the domain provider if you cannot find DNS settings, cannot identify how its interface represents the root host, or find records you do not understand. Google’s Blogger guide directs users to the domain provider when custom-domain setup problems continue.
Give the provider a precise description: the custom www address works in Blogger, while the bare domain must use Blogger’s documented naked redirect. Ask where to manage root A records and whether another active root record conflicts with them. The provider can explain its own interface and the current records on the domain.
Do not ask the provider to replace records blindly. A root-domain record may support something outside Blogger. Check its purpose first, especially if the domain has ever pointed to a different website or hosting service.
Keep the three checks separate
A reliable Blogger custom-domain setup has three distinct checks. The selected subdomain must connect to Blogger. The bare domain must have the four A records in Google’s documented procedure. Blogger’s Redirect domain setting must point readers from the root address to the custom address.
That is why www can work while the bare domain does not. The first check has passed. The other two still need attention.
Which custom address is saved in your Blogger Publishing settings? Do the root-domain records match Google’s four A-record values, and is Redirect domain turned on for that blog?