Connect a domain to Blogger using its DNS records, then check redirects and HTTPS.
a.
Ashwathanarayana K P
2 min read
A custom domain gives a Blogger blog an address such as www.example.com while Blogger continues hosting the blog. You need administrator access to the blog and access to the domain's DNS settings. The DNS provider is often the company where you bought the domain, but it can be a different service.
Before changing records, note any existing website or email configuration. Changing the wrong DNS records can interrupt those services. If the domain already hosts a site, plan the transition with its provider before repointing it.
Add the address in Blogger
FILE
Your Crate
Size
—
Uploaded
—
Type
—
Waybill
—
SHA-256
—
Sign in to Blogger and select the blog.
Open Settings and find Publishing.
Select Custom domain, enter your chosen subdomain, such as www.example.com, and save.
Blogger displays two CNAME records that you must add at your DNS provider.
A CNAME is a DNS record that points one hostname to another. Blogger requires a subdomain such as www or blog; its settings guide says the blog itself cannot be hosted at the bare domain, such as example.com.
Add the DNS records
Open the DNS management page for your domain. Add the first CNAME using the subdomain as its name and the destination shown by Blogger. Add the second security CNAME using the unique name and destination shown for your blog. Copy both values carefully; the verification record is specific to your account and blog.
Google's custom domain instructions currently give ghs.google.com as the first destination. Follow the values displayed in your own Blogger settings if instructions change. DNS interfaces vary: some automatically append your domain name, so check your provider's guidance rather than duplicating it in the host field. Do not remove unrelated mail records.
Wait for DNS to update, then return to Blogger and save the custom domain again. Google says to wait at least an hour before retrying; DNS changes may take longer. If verification fails, compare both CNAME names and destinations with Blogger's screen and check for a conflicting record on the same hostname.
Check the bare domain and HTTPS
If you want example.com to reach www.example.com, follow Blogger's current instructions for redirecting the bare domain. That can require additional DNS records, so use the values in the official guide and check for conflicts with an existing site first.
In Blogger's HTTPS settings, check availability and enable HTTPS redirect when it is available. If your domain uses CAA records, Google says they must allow letsencrypt.org for certificate creation and renewal. Ask your DNS provider if you are unsure whether those records apply.
Open the custom address in a fresh browser window and visit a few posts and images. Check the bare-domain redirect if configured, then confirm the browser uses HTTPS. Google notes that the old Blogspot address can take up to 24 hours to redirect to the custom domain. Keep both the domain registration and access to your DNS provider current.
