Pointing a custom domain at a Blogger (Blogspot) blog needs records in two places: your DNS Manager here at SakuraHost, and your Blogger dashboard itself. Blogger's own setup screen only ever shows you a CNAME — it never lists the four A record IP addresses you need for the root domain (no "www") to work. This guide covers both sides.
Step 1: Add the four A records
These four A records point your root domain (yourdomain.co.tz, no "www") at Google's Blogger servers. Add all four as separate records, same name, same type, different IP each time — DNS Manager allows multiple A records on one name, so don't try to combine them into a single record.
| Type | Name | Content (IP) |
|---|---|---|
| A | @ (or leave blank for the root domain) | 216.239.32.21 |
| A | @ | 216.239.34.21 |
| A | @ | 216.239.36.21 |
| A | @ | 216.239.38.21 |
Step 2: Add the www CNAME
In DNS Manager, add a CNAME record: www pointing to ghs.google.com.
Step 3: Get your verification CNAME from Blogger
www.yourdomain.co.tz.
www CNAME above), wait 5–15 minutes, then go back to Blogger and save www.yourdomain.co.tz again. It should verify successfully this time.
Step 4: Enable HTTPS
In Blogger → Settings, toggle HTTPS availability and HTTPS redirect to Yes. Google provisions a free SSL certificate for your domain automatically — this can take up to 24 hours to become available after your domain first verifies.
Step 5: Redirect the root domain
To make yourdomain.co.tz (no www) redirect to www.yourdomain.co.tz, enable Redirect domain in Blogger's Publishing settings. This only works once the four A records from Step 1 are live.
Nameservers
Make sure your domain's nameservers are set to SakuraHost's: ns5.sakurahost.co.tz and ns6.sakurahost.co.tz. If they're pointed elsewhere, DNS Manager changes won't take effect at all.
- "Cannot verify authority" in Blogger — wait 15–30 minutes for DNS to propagate, then try saving again. Use our WHOIS & DNS Check tool or
dig www.yourdomain.co.tz CNAMEto confirm the verification CNAME is actually live before retrying. - Site not loading on the bare domain — check all four A records are present and none are missing or mistyped.
- HTTPS not available — this can take up to 24 hours after the domain first verifies; it's normal, not a sign something's broken.
- Domain used to host something else — remove any old A or CNAME records on
@andwwwfirst. Conflicting records on the same name cause unpredictable behaviour.