How to Set Up Your Blogger Blog With a Custom Domain

Blogger gives every blog a free .blogspot.com address, but a custom domain — like www.yourblogname.com — looks more professional, is easier for people to remember, and gives you full ownership over your blog's identity if you ever decide to move platforms later.

Connecting a custom domain to Blogger comes down to one core task: telling your domain's DNS settings to point at Google's servers. The exact screens will look slightly different depending on where you bought your domain (GoDaddy, Namecheap, Google Domains, IONOS, Hostinger, and so on), but the actual records you need to add are identical everywhere, since they come from Blogger itself. This guide walks through that universal process.

Before You Start

You'll need:

• A Blogger blog you already own
• A domain name purchased from any domain registrar
• Access to that registrar's DNS management panel (sometimes called "DNS Zone Editor," "Advanced DNS," or "Name Server Management")

Have both Blogger and your registrar's dashboard open in separate tabs — you'll be copying values back and forth between them.

Step 1: Get Your CNAME Records From Blogger

1. Sign in to Blogger and select your blog.
2. In the left-hand menu, click Settings.
3. Under the "Publishing" section, click Custom domain.
4. Enter the domain you purchased, including the www. prefix — for example, www.yourblogname.com — and click Save.

Blogger will show an error at this point. That's expected — it's telling you the DNS records don't exist yet, and it's giving you the two records you need to create:

• Blog CNAME — Name: www (or whichever subdomain you're using), Destination: ghs.google.com
• Security CNAME — a unique Name and Destination pair specific to your blog and Google account, generated only for you

Keep this Blogger tab open, or copy both values into a text file — you'll need them in the next step.

Step 2: Add the CNAME Records at Your Domain Registrar

1. Log in to the account where you purchased your domain.
2. Find the DNS management section — most registrars label it something like "DNS Settings," "DNS Zone Editor," or "Advanced DNS."
3. Add a new CNAME record:
   • Host/Name: www
   • Points to/Destination: ghs.google.com
4. Add a second CNAME record using the unique verification values Blogger gave you in Step 1 (Name and Destination will look like random strings ending in .domainverify.googlehosted.com or similar).
5. Save your changes.

If a CNAME record for www already exists (some registrars add one automatically when you buy a domain), delete or edit the existing one rather than creating a duplicate — most DNS systems won't allow two CNAME records with the same host name.

Step 3: Wait for DNS to Propagate

DNS changes aren't instant. Google recommends waiting at least an hour before trying again, though full propagation across the internet can occasionally take up to 24 hours. Go back to Blogger's Custom Domain settings and re-enter your domain to confirm it saves without an error. If it still fails after an hour, double-check that the CNAME values were entered exactly as shown — a single typo in a long verification string is the most common cause of a stuck setup.

Step 4 (Optional): Redirect the Naked Domain

By default, this setup makes your blog reachable at www.yourblogname.com. If you also want yourblogname.com (without the "www") to work and redirect properly, you'll need to add four A records at your domain registrar, pointing to Google's IP addresses:

216.239.32.21
216.239.34.21
216.239.36.21
216.239.38.21

Leave the "Host" field empty (or use @, depending on your registrar's convention) when adding these. If any A records already exist for your root domain, remove them first — having conflicting A records is a common reason a "naked domain" redirect fails to work.

Once the A records are saved, go back to Blogger:

1. Go to Settings.
2. Under "Publishing," turn on Redirect domain (this redirects yourblogname.com to www.yourblogname.com).

A Few Things Worth Knowing

• SSL/HTTPS is automatic. Once your custom domain is verified, Blogger provisions an SSL certificate for you at no cost — you don't need to buy or configure one separately.
• If you use CAA records (a DNS record type that restricts which certificate authorities can issue SSL certificates for your domain), you'll need to explicitly add an entry allowing letsencrypt.org, or Blogger won't be able to issue or renew your certificate.
• Email service on your domain is unaffected by these changes as long as you only add the specific CNAME and A records described above — you're not changing your domain's nameservers, just adding a few targeted records. If you use email hosted on the same domain, avoid deleting any existing MX records while you make these changes.
• This won't disable an existing website on the same domain either, since you're only editing individual records rather than pointing your whole domain elsewhere — provided your registrar's DNS panel supports adding these records directly (nearly all modern ones do).

That's the entire process. Once DNS propagates and Blogger stops showing an error, your blog will be live on your own domain — no registrar-specific workaround needed.