Custom Domain DNS Setup Helper for Blogger – Free DNS Configuration Tool

① Custom Domain DNS Setup Helper for Blogger

How to Use This DNS Setup Tool

Quick Start:

1. Enter your domain name and BlogSpot URL in Section 1
2. Select your domain registrar
3. Click "Generate DNS Records" to get your exact configuration
4. Copy the records and add them to your registrar's DNS panel
5. Follow the step-by-step guide for your specific registrar

Section 1: Domain Information

Custom Domain Name

BlogSpot URL

Domain Registrar GoDaddy Namecheap Google Domains Cloudflare Hostinger Others

Section 2: DNS Records Generator

Section 3: Blogger Settings Configuration

Click "Generate DNS Records" above first, then this section will show your Blogger settings.

Section 4: SSL / HTTPS Setup Guide

Good News: Google handles SSL certificates automatically for Blogger custom domains. However, there are important things to know:

1. Automatic SSL: After DNS propagates (up to 48 hours), Google automatically provisions an SSL certificate for your domain.
2. HTTPS Redirect: Go to Blogger > Settings > HTTPS and set "HTTPS Availability" to "Yes". Then enable "HTTPS Redirect".
3. Mixed Content Fix: If some resources load over HTTP, images may show as "not secure". Ensure all images use HTTPS URLs.
4. Check HTTPS Status: Visit SSL Labs to test your domain's SSL certificate.
5. Redirection Chain: After enabling HTTPS, your site should redirect: http:// → https:// automatically.

Section 5: Domain Redirect Helper

Redirect Type www to non-www non-www to www HTTP to HTTPS Old Domain to New Domain

Old Domain

New Domain

Section 6: Multiple Domain Support

Primary Domain

Secondary / Old Domain

Advanced DNS Configuration

DNS Propagation

MX Records

SPF/DKIM/DMARC

Subdomains

TXT Verification

www vs non-www

DNS Propagation Checker

DNS changes can take anywhere from a few minutes to 48 hours to propagate worldwide. This is because DNS records are cached at multiple levels.

What affects propagation time:

• TTL Value: Lower TTL = faster propagation when making changes
• Registrar Speed: Some registrars push updates faster
• ISP Cache: Your ISP may cache old DNS records
• Browser Cache: Clear your browser cache to see changes faster

Check DNS Propagation:

• WhatsMyDNS.net — Global DNS propagation checker
• DNSChecker.org — Real-time DNS propagation map
• Google: What is my DNS
• MXToolbox DNS Lookup
• IntoDNS — Comprehensive DNS health report

Important: Do NOT make additional DNS changes while waiting for propagation. This resets the timer and can cause conflicts.

Command Line DNS Check

Windows:
  nslookup yourdomain.com
  nslookup www.yourdomain.com

macOS / Linux:
  dig yourdomain.com
  dig www.yourdomain.com CNAME
  dig yourdomain.com +short A

MX Records for Custom Email

If you want email at you@yourdomain.com, you need MX records. Common email providers:

Google Workspace (Gmail) MX Records

Priority	Host	Value
1	@	ASPMX.L.GOOGLE.COM
5	@	ALT1.ASPMX.L.GOOGLE.COM
5	@	ALT2.ASPMX.L.GOOGLE.COM
10	@	ALT3.ASPMX.L.GOOGLE.COM
10	@	ALT4.ASPMX.L.GOOGLE.COM

Zoho Mail MX Records

Priority	Host	Value
10	@	mx.zoho.com
20	@	mx2.zoho.com
50	@	mx3.zoho.com

Note: Adding MX records for email is separate from Blogger DNS setup. You can have both. MX records handle email, CNAME/A records handle your website.

Email Authentication Records

Protect your domain from email spoofing and improve deliverability.

SPF Record (TXT)

SPF (Sender Policy Framework) tells receiving servers which mail servers are authorized to send email from your domain.

Your Email Provider Google Workspace Zoho Mail Microsoft 365 / Outlook Mailgun Custom

Custom SPF Include

DKIM Record (TXT)

DKIM adds a digital signature to outgoing emails. Set this up in your email provider's dashboard, then add the TXT record they provide to your DNS.

How to set up DKIM:

1. Log into your email provider (Google Workspace, Zoho, etc.)
2. Navigate to Email Settings > Authentication > DKIM
3. Generate a new DKIM key
4. Add the provided TXT record to your DNS
5. Verify / Enable DKIM signing

DMARC Record (TXT)

DMARC tells receivers what to do with emails that fail SPF/DKIM checks.

DMARC Policy none (monitor only) quarantine (spam folder) reject (block failed emails)

Report Email (for aggregate reports)

Subdomain Setup Guide

You can use subdomains with Blogger or point them elsewhere.

Common Subdomain Configurations

blog.example.com (Separate Blogger Blog)

Type	Host	Value
CNAME	blog	ghs.google.com

Then in Blogger Settings > Publishing, set custom domain to: blog.example.com

shop.example.com (External Service)

Type	Host	Value
CNAME	shop	shops.myecommerce.com

Point to your e-commerce provider's CNAME target.

mail.example.com (Webmail)

Type	Host	Value
CNAME	mail	mail.youremailprovider.com

www.example.com (Blogger with Subdomain Path)

Type	Host	Value
CNAME	www	ghs.google.com

This is the standard Blogger setup — your main blog lives at www.example.com

Subdomain Tips:

• CNAME records are the standard for subdomains pointing to external services
• A records can also be used to point subdomains to an IP address
• Wildcard CNAME (*.example.com) is supported by some registrars
• Each subdomain can have its own SSL certificate

TXT Records Verification Guide

TXT records are used for domain verification, email security, and more.

Common TXT Record Uses

Purpose	Host	Value (Example)
Google Search Console	@	google-site-verification=XXXXXXXXXX
Google Workspace	@	v=spf1 include:_spf.google.com ~all
Domain Ownership	@	site verification code from provider
DMARC	_dmarc	v=DMARC1; p=none; rua=mailto:admin@example.com
DKIM	selector._domainkey	v=DKIM1; k=rsa; p=MIGfMA...

How to Add TXT Records

1. Log into your domain registrar's DNS management panel
2. Find "Add Record" or "Add TXT Record"
3. Set the Type to TXT
4. Enter the Host/Name value (usually @ or a specific subdomain)
5. Paste the Value/Text content exactly as provided
6. Save and wait for DNS propagation

Verification Tip: After adding a TXT record, you can verify it using: nslookup -type=TXT yourdomain.com or use MXToolbox TXT Lookup

www vs non-www Decision Guide

Choosing between www.example.com and example.com affects your site's URL structure.

✔ www (Recommended)

• Industry standard for most websites
• Blogger's preferred setup
• Clear separation: www = website, non-www = other services (email, FTP)
• Easier DNS management with CNAME
• Cookie scope limited to www subdomain
• Better CDN compatibility
• Universally recognized as a website URL

✘ Non-www (Naked Domain)

• Requires A records (not CNAME) at root
• Cookies apply to entire domain + subdomains
• Some services may not support root CNAME
• Less conventional for general users
• DNS changes at root are slower to propagate

Blogger Recommendation: Use www as your primary domain. Blogger handles the www setup natively with CNAME records. The non-www version can be redirected to www automatically.

How Blogger Handles www/non-www

Blogger uses www as the canonical URL by default:

1. Set your custom domain to www.example.com in Blogger
2. Blogger automatically redirects example.com to www.example.com
3. All internal links use the www version
4. This ensures consistent URLs and proper SEO

Important: Never add both a CNAME and A records for the same host. This creates DNS conflicts. For Blogger, use:

• CNAME for www → ghs.google.com
• A records for @ (root) → Google's IPs

Complete Custom Domain Setup Guide for Blogger

1. 1Purchase a Domain — Buy from any registrar (GoDaddy, Namecheap, Cloudflare, etc.)
2. 2Find Your DNS Management Panel — Each registrar has a different location (see registrar-specific guides below)
3. 3Add CNAME Record — Host: www, Value: ghs.google.com
4. 4Add A Records — Four records pointing to Google's IPs at the root (@)
5. 5Wait for DNS Propagation — Can take up to 48 hours (usually 1-4 hours)
6. 6Configure Blogger — Go to Settings > Publishing > Custom Domain, enter your www domain
7. 7Enable HTTPS — In Blogger Settings, enable HTTPS availability and redirect
8. 8Verify — Visit your domain and confirm it loads your blog

DNS Records Explained

Record Type	Purpose	Example
A	Points a hostname to an IPv4 address	@ → 216.239.32.21
CNAME	Alias of one hostname to another	www → ghs.google.com
MX	Routes email to mail servers	@ → ASPMX.L.GOOGLE.COM
TXT	Text records for verification & security	@ → v=spf1 include:... ~all
NS	Nameservers that manage your DNS	ns1.example.com
AAAA	Points hostname to IPv6 address	@ → 2001:4860:4802::32
SRV	Service records for specific protocols	_sip._tcp → server.example.com
CAA	Specifies which CAs can issue SSL certs	@ → 0 issue "letsencrypt.org"

For Blogger Custom Domain, you only need:

• 1 CNAME record for www
• 4 A records for @ (root domain)

Everything else (email, subdomains, etc.) is optional.

Step-by-Step Registrar DNS Setup Guides

GoDaddy

Namecheap

Cloudflare

Step-by-Step: GoDaddy DNS Setup for Blogger

1. Log in to GoDaddy — Go to godaddy.com and sign in
2. Go to My Products — Click your username > "My Products"
3. Select Your Domain — Click "DNS" next to your domain
4. Scroll to DNS Management — You'll see existing records
5. Delete Existing Records (if conflicting):
   • Remove any existing www CNAME or A record
   • Remove any existing @ CNAME record
   • Keep MX records if you use GoDaddy email
6. Add CNAME Record:
   • Click "Add" > select "CNAME"
   • Host: www
   • Points to: ghs.google.com
   • TTL: 1 Hour (or default)
7. Add A Records:
   • Click "Add" > select "A"
   • Host: @, Points to: 216.239.32.21
   • Repeat for: 216.239.34.21, 216.239.36.21, 216.239.38.21
   • TTL: 1 Hour for each
8. Save — Click "Save" to confirm all changes
9. Wait — DNS changes may take up to 48 hours (GoDaddy is usually 1-4 hours)

GoDaddy Specific Notes:

• GoDaddy may try to upsell their website builder — decline it
• If you see "Parked" or "For Sale" page, DNS hasn't propagated yet
• GoDaddy's default TTL is 1 hour — this is fine for Blogger
• Some GoDaddy domains have "Domain Connect" — do NOT use it for Blogger

Step-by-Step: Namecheap DNS Setup for Blogger

1. Log in to Namecheap — Go to namecheap.com and sign in
2. Go to Domain List — Click "Domain List" from the left sidebar
3. Click "Manage" — Next to your domain
4. Go to "Advanced DNS" tab
5. Turn off Namecheap BasicDNS features:
   • Disable "Domain Name Server Setup" if it points to Namecheap's parking
   • The DNS should be on Namecheap's BasicDNS for CNAME to work
6. Add CNAME Record:
   • Click "ADD NEW RECORD"
   • Type: CNAME Record
   • Host: www
   • Value: ghs.google.com
   • TTL: Automatic
7. Add A Records:
   • Click "ADD NEW RECORD"
   • Type: A Record
   • Host: @, Value: 216.239.32.21
   • Repeat for: 216.239.34.21, 216.239.36.21, 216.239.38.21
   • TTL: Automatic for each
8. Check for URL Redirect Records:
   • If Namecheap has a "URL Redirect Record" for www, delete it
   • This conflicts with your CNAME record
9. Save All Changes
10. Wait — Usually takes 30 minutes to 6 hours with Namecheap

Namecheap Specific Notes:

• Namecheap sometimes adds a "URL Redirect" for www — you MUST delete this before adding CNAME
• If using Namecheap PremiumDNS or third-party DNS, the interface may differ
• Namecheap free WhoisGuard won't affect DNS

Step-by-Step: Cloudflare DNS Setup for Blogger

1. Log in to Cloudflare — Go to dash.cloudflare.com
2. Select Your Domain from the dashboard
3. Go to "DNS" > "Records"
4. Delete Conflicting Records:
   • Remove any existing www A, AAAA, or CNAME records
   • Remove any existing @ CNAME records
5. Add CNAME Record:
   • Click "Add Record"
   • Type: CNAME
   • Name: www
   • Target: ghs.google.com
   • Proxy status: DNS only (grey cloud) — Blogger handles SSL
   • TTL: Auto
6. Add A Records:
   • Click "Add Record"
   • Type: A
   • Name: @
   • IPv4: 216.239.32.21
   • Proxy status: DNS only (grey cloud)
   • Repeat for: 216.239.34.21, 216.239.36.21, 216.239.38.21
7. Save

Cloudflare Critical Notes:

• Turn OFF the orange cloud (Proxy) for ALL Blogger records — Blogger requires direct DNS, not proxied
• Do NOT enable "Always Use HTTPS" in Cloudflare Page Rules — Blogger handles this
• Do NOT enable Cloudflare's "Flexible SSL" — it will conflict with Blogger's SSL
• Cloudflare proxy adds extra headers and caching that can break Blogger
• If you need Cloudflare features (WAF, caching), consider using Cloudflare only for non-Blogger subdomains

Troubleshooting DNS Issues

Problem	Cause	Solution
"Server not found" / NXDOMAIN	DNS not propagated or wrong nameservers	Wait up to 48h. Check nameservers point to your registrar.
Shows registrar parking page	DNS not pointing to Google yet	Verify CNAME and A records are saved correctly.
404 Error from Blogger	Domain not configured in Blogger	Add domain in Blogger Settings > Publishing.
"Another blog is already hosted at this address"	Domain claimed by another blog	Remove from other blog first, or use Google's recovery form.
Mixed content warnings	Images/resources loading over HTTP	Update image URLs to use HTTPS.
"Too many redirects"	Conflicting redirect settings	Check both Blogger and registrar redirect settings.
Works with www but not without	Missing or wrong A records	Verify all 4 A records at @ are correct.
Intermittent "server error"	DNS partially propagated	Wait. Use whatsmydns.net to check global propagation.
SSL certificate error	HTTPS not enabled or not ready	Enable HTTPS in Blogger Settings. Wait up to 48h after DNS.
Cloudflare infinite redirect loop	Proxy enabled on Blogger records	Turn off Cloudflare proxy (grey cloud) for www and @.

Common DNS Mistakes to Avoid

Top 10 DNS Setup Mistakes for Blogger:

1. Typo in CNAME value — Must be exactly ghs.google.com (not ghs.google.com. with trailing dot, unless your registrar adds it automatically)
2. Using A record instead of CNAME for www — www should be CNAME, @ should be A records
3. Forgetting all 4 A records — Google requires all 4 IP addresses at the root domain
4. Not waiting for propagation — DNS changes take time. Be patient!
5. Conflicting records — Having both CNAME and A record for the same host
6. Wrong Host value — Using @ for CNAME instead of www
7. Enabling Cloudflare proxy — Must use DNS-only (grey cloud) mode
8. Not setting up Blogger first — Configure Blogger after DNS is ready, not before
9. Using registrar's redirect feature — Delete URL redirect records, use DNS records only
10. Adding www prefix in Blogger wrong — Enter www.example.com not just example.com

FAQ Section