How to Connect a Custom Domain to Blogger and Enable HTTPS

Short answer: in Blogger, enter a subdomain such as www.tenmiencuaban.com to retrieve the correct two CNAME records. Add those records wherever your DNS is managed; add the four A records for the root domain only if you need to redirect from tenmiencuaban.com to www.tenmiencuaban.com. Once Blogger has accepted the domain, wait for HTTPS Availability to be ready before enabling HTTPS Redirect. Finally, check the URLs in a private browsing window.

This guide is for beginners who have administrative access to a Blogger blog and permission to edit the domain’s DNS. The target outcome is for the subdomain to open the blog over HTTPS; for the root domain to redirect correctly if you configured it; for one public post and one public Page to open; and for you to know how to restore records if another service is affected.

Example limitation: www.tenmiencuaban.com is only a placeholder. SaibABC.Com is the WordPress website publishing this series, while SaibABC Blog is the planned illustrative Blogger project. This article does not claim that SaibABC Blog already has a domain, has been connected, or has achieved any real-world result. Do not use SaibABC.Com’s DNS for practice.

Prepare access and record the current DNS configuration

You need two separate permissions: administrative access to the correct blog in your Google Account and permission to manage the DNS zone at your domain provider. DNS (Domain Name System) is the system that directs a domain to the corresponding service. Blogger is operated by Google, so this procedure does not require you to manage a server, database, PHP, PHP-FPM, or a separate web server.

Sign in to the correct Google Account and verify that you have selected the correct blog before making changes.
Open the DNS management page, which may be called DNS Records, Manage DNS or Zone Editor.
Determine whether the domain is currently used for email, a website, an online store, or any verification service.
Take a screenshot or copy the current record list, including the type, host, value, and TTL if the interface displays it.
Store this backup in a secure location; do not include verification codes or login information in an article, public image, or message from an untrusted source.

If the domain currently serves another email service or website, do not replace its existing records yet. In particular, do not delete the entire DNS zone to “start over.” The pre-change backup is your recovery point if configuring Blogger has an unintended effect.

Retrieve the records directly from Blogger

Perform this step in the Blogger dashboard in a browser:

Open the blog you want to configure and go to Settings.
Find the Publishing section and select Custom domain.
Enter the subdomain, for example www.tenmiencuaban.com, then select Save or Confirm.
Record the two CNAME records that Blogger displays: one record connects the subdomain, and the other is a separate verification record.

The first CNAME usually has the host www and points to ghs.google.com. The second CNAME is a name-and-value pair generated by Blogger for your blog. Use the pair exactly as shown on the current screen; do not copy it from another blog or guide, or create a verification string yourself (according to Blogger Help, https://support.google.com/blogger/answer/1233387?hl=en-uk).

Type	Host or name	Value	How to handle it
CNAME	`www` or the host you chose	`ghs.google.com`	Enter it exactly as required by the DNS interface
CNAME	[chuỗi Blogger hiển thị]	[giá trị Blogger hiển thị]	Copy it exactly for verification

If your DNS provider automatically appends the full domain name, you may need to enter only the host portion. For example, the Host field may require only www, not the full www.tenmiencuaban.com. When you are unsure, check the note beside the input field or the DNS provider’s documentation instead of guessing.

Configure the CNAME records and root domain at your DNS provider

Do this on the DNS management page, not in the Blogger post editor:

Choose Add record CNAME.
Enter the host www or the subdomain host you used in Blogger.
Enter the target ghs.google.com for the connection CNAME.
Create the second CNAME using the exact host and verification value provided by Blogger.
Save the changes and record when you made them.

Do not configure the same host with both a CNAME and a conflicting record. If www already has a CNAME pointing to another service, first identify that service and record the old value. Make the change only after you have decided to move this host to Blogger.

When do you need four A records?

The subdomain and the root domain are two different addresses. If you want readers to open tenmiencuaban.com and then be redirected to www.tenmiencuaban.com, Blogger instructs you to add the following four A records for the host @ or leave the field blank, depending on your provider:

216.239.32.21
216.239.34.21
216.239.36.21
216.239.38.21

Add these four addresses only if you need to redirect the root domain and the existing A records do not serve another website, server or service. If the root domain is currently used by another website, replacing those records could redirect that website to Blogger or cause the service to stop working. Blogger also notes that records and redirects may take time to take effect across different DNS servers.

Host	Type	Before the change	After the change	Check
`www`	CNAME	[giá trị cũ hoặc chưa có]	`ghs.google.com`	[ ]
[chuỗi Blogger]	CNAME	[chưa có]	[giá trị Blogger cung cấp]	[ ]
`@`	A	[các giá trị hiện tại]	[bốn IP nếu cần chuyển hướng]	[ ]

Text in square brackets is information for you to fill in. It is not a verified result for SaibABC Blog.

Verify the domain in Blogger before switching to HTTPS

Return to Settings > Publishing > Custom domain in Blogger and re-enter the subdomain if the interface requests it. When Blogger detects the correct verification CNAME, the connection status will change. If it does not, check the host, dots, target value and conflicting records in turn; do not delete records and add a large number of alternatives.

DNS updates do not necessarily propagate in the same way across all networks or devices. Blogger’s documentation states that redirecting from a blogspot.com address to a custom domain can take up to 24 hours; during this period, some addresses may not produce the same result (according to Blogger Help).

Not verified: Compare the second CNAME with the Blogger screen for the correct blog.
www does not open: Check the CNAME for host www and any old conflicting record.
www opens but the root domain does not: Check the four A records and the domain redirect option.
The Blogspot address still opens: This does not by itself prove that DNS is broken; check the final URL and wait for the system to apply the changes.

Enable HTTPS in the correct order

HTTPS is a version of HTTP that encrypts the connection between the browser and the service. For a custom domain, do the following in Blogger:

Open Settings > HTTPS.
Set HTTPS Availability to Yes when the option is ready.
Wait until the HTTPS Availability status is ready, then enable HTTPS Redirect.
Record the status and final URL so you can check them outside the administration interface.

Do not enable HTTPS Redirect before HTTPS Availability is ready. Blogger may need to issue a certificate after DNS points correctly; you do not install a certificate on a separate server yourself in this process.

If the domain has CAA (Certification Authority Authorization), this is a DNS record that limits which certificate authorities are allowed to issue certificates. Check CAA only when the domain actually has such a record or Blogger reports a related error. In that case, compare the authorization requirement letsencrypt.org with the official documentation instead of adding records based on examples found online (according to Blogger Help, https://support.google.com/blogger/answer/6284029?hl=en).

You can also consult the guide to enabling HTTPS and troubleshooting CAA errors if you need a more in-depth analysis of certificate-related errors. For the current article, you only need to determine the status, check CAA when there is a basis for doing so, and know when not to continue modifying DNS.

Check from the reader’s perspective

Do this after DNS has had time to propagate and HTTPS Availability is ready. Open a private window or a browser where you are not signed in, so you do not confuse administrator privileges with public access.

Address or content	Expected result	Pass
`https://www.tenmiencuaban.com`	The home page opens, the URL uses HTTPS, and the browser shows no certificate warning	[ ]
`http://www.tenmiencuaban.com`	Redirects to HTTPS if HTTPS Redirect is enabled	[ ]
`https://tenmiencuaban.com`	Redirects to the subdomain if the root domain and Redirect domain have been configured	[ ]
A public post	The correct content opens, with no errors in images or internal links	[ ]
A public Page, if the blog has one	Opens without unexpectedly requiring sign-in	[ ]
The old Blogspot address	Redirects to the custom domain after the system has applied the changes	[ ]

In addition to the padlock icon, record the final URL after each redirect. If the URL is still http://http://, the browser shows a certificate error, or the root domain opens a different service, do not mark HTTPS as complete. If access to the blog or post is restricted, the private window may request sign-in; check the reading permissions instead of concluding that DNS is faulty.

Common errors, safe fixes, and rollback

Symptom	Cause to check	Safe handling
Blogger has not verified the domain	The second CNAME is incorrect, missing, or belongs to another blog	Retrieve the pair of values from Custom domain in the correct blog, update the record accurately, and wait for propagation
`www` does not open	The host is incorrect, the destination is not `ghs.google.com` , or an existing CNAME conflicts	Compare each field, record the old value, and modify only the host being moved to Blogger
The root domain does not redirect	An A record is missing, the host is set incorrectly `@` , or Redirect domain has not been enabled	Check the four A records, the Redirect domain status, and the services using the root domain
HTTPS is not ready	DNS has not stabilized, or CAA restricts the certificate authority	Check CAA when there is a basis for doing so, do not enable HTTPS Redirect prematurely, and do not modify multiple groups of DNS records at once
Another email service or website has stopped working	A record unrelated to Blogger was deleted or replaced	Stop making changes, compare the before-and-after records, and restore the old record according to the DNS provider’s documentation

A safe rollback means restoring the affected records to the values recorded before the change, not deleting the entire DNS zone. If HTTPS Redirect causes errors while HTTPS is not ready, disable HTTPS Redirect, preserve the current state to identify the cause, and enable it again only after HTTPS Availability is ready. Remove the custom domain from Blogger only after recording its status and understanding the impact; do not delete the domain registration or DNS zone to try again.

Result-verification exercise

Apply this to your own domain; you do not have to use the SaibABC name:

Record the subdomain you will use, such as www.tenmiencuaban.com.
Copy the two CNAME records displayed by Blogger, clearly marking the connection CNAME and the verification CNAME.
Complete the before-and-after DNS table, including any records used by other email or website services.
Record the status of HTTPS Availability and HTTPS Redirect.
Open the URLs in a private browsing window and record the final URL after redirection.
Mark one post and one public Page as successfully opened, if the blog has a Page.

The exercise is complete only when the subdomain opens over HTTPS, the root domain redirects correctly if you configured it, public content opens, and you know which records must be restored. This result only confirms that the access path is working; it does not prove that the blog has readers, has been indexed, or has search rankings.

Next step

If all URLs are working, keep the DNS table, HTTPS status, and test date for reference when renewing the domain or changing services. If problems remain, do not reconfigure everything from scratch. Save the error message, affected URL, current records, records from before the change, and the update time. This information will be used to classify record, verification, redirection, or HTTPS issues in the next troubleshooting article in the series: Fix Blogger Custom-Domain Errors Before Changing DNS or HTTPS

Connect a Custom Domain to Blogger and Verify HTTPS Correctly