How to Connect a Custom Domain to WordPress.com (DNS Setup Guide)

If you’ve decided to put your WordPress.com site on a custom domain, good call. A clean domain makes your brand look credible, improves click-through rates, and lets you control your email. The catch? You have to hook up DNS correctly. The good news: it’s not hard once you know which path to choose. Think of DNS as the internet’s phone book—point your name to the right address, and the web finds you instantly.

This guide walks you through the fastest, most reliable ways to connect your domain to WordPress.com, with clear steps, gotchas to avoid, and a few up-to-date industry notes you’ll be glad you knew ahead of time.

What You’re Actually Doing When You “Connect a Domain”

– Your domain registrar is where you bought the domain (e.g., WordPress.com, Namecheap, GoDaddy, Cloudflare, Squarespace Domains—formerly Google Domains customers moved there in 2023).
– DNS hosting is the service that stores your DNS records. It might be your registrar, WordPress.com, or another provider.
– To connect your domain to a WordPress.com site, you either:
1) Use WordPress.com as your DNS host by changing nameservers, or
2) Keep DNS where it is, but add A and CNAME records that point the domain to WordPress.com.

Both work. The nameserver route is simpler and more “set it and forget it.” The A/CNAME route is handy if you already run complex DNS elsewhere or use a service like Cloudflare.

Choose Your Path

– Best for most people: Change nameservers to WordPress.com. Simple, reliable, auto SSL, and WordPress.com can manage your DNS later if you need email or subdomains.
– Best if you already manage DNS elsewhere: Point A and CNAME records only. Useful if you run email, subdomains, or complex integrations with an existing DNS provider.

Before You Start: Quick Checklist

– You have a WordPress.com site ready.
– You’ve added a plan that supports custom domains (WordPress.com typically requires a paid plan for domain mapping).
– You own the domain and can log in to your registrar.
– If you’re using email with a third party (Google Workspace, Microsoft 365, Zoho), you know your MX/DKIM/SPF/DMARC records. You’ll re-check these after moving DNS.
– Optional: Lower the TTL of your existing DNS records (e.g., to 300 seconds) a day before changes for faster propagation.

Step 1: Add the Domain in WordPress.com

– In WordPress.com, go to My Home > Upgrades > Domains.
– Choose Use a domain I own.
– Enter your domain and select Connect your domain.
– WordPress.com will offer two options: change nameservers or update DNS records. Pick the one you decided on above. Keep the instructions open—you’ll need the values in the next step.

Option A: Change Nameservers to WordPress.com

This tells the internet: “WordPress.com is now the authority for my domain’s DNS.”

Change nameservers at your registrar

– Log in to your registrar’s dashboard.
– Find your domain’s Nameservers or DNS settings.
– Replace the existing nameservers with:
– ns1.wordpress.com
– ns2.wordpress.com
– ns3.wordpress.com
– Save, confirm, and look for success messages.

Notes:
– If DNSSEC is enabled with your current DNS provider, remove the DS record at the registrar before changing nameservers. A mismatched DS record breaks resolution. You can re-enable DNSSEC with WordPress.com later if supported.
– Propagation takes anywhere from 15 minutes to 48 hours (typically under a few hours).

Verify and finish in WordPress.com

– Go back to WordPress.com > Domains > your domain.
– WordPress.com will detect the nameservers. When it’s active, you’ll see it marked as the Primary domain (or set it as primary).
– Free SSL is issued automatically. Allow up to several hours for the certificate to appear. If it’s stuck, ensure the domain resolves to WordPress.com (check with a DNS checker) and try toggling HTTPS settings once the domain is live.

Re-add email DNS (if needed)

If you use third-party email and you moved nameservers, add those records in WordPress.com > Domains > DNS Records:

– MX: Provided by your email hosting (e.g., Google Workspace MX set).
– SPF: TXT record typically like v=spf1 include:_spf.google.com ~all (adjust to your provider).
– DKIM: Usually CNAMEs from your email provider.
– DMARC: TXT at _dmarc with a policy like v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com

Tip: If you’re just starting email, set p=none first to monitor, then move to quarantine or reject once you’ve verified alignment.

Option B: Keep DNS Elsewhere and Point Records to WordPress.com

This keeps your DNS host the same but routes web traffic to WordPress.com.

– In your DNS provider’s dashboard, add:
– A record @ pointing to 192.0.78.24
– A record @ pointing to 192.0.78.25
– CNAME record for www pointing to your root domain (e.g., www -> example.com)

Notes:
– If your provider requires a host value, “@” typically means the root domain (example.com).
– Remove old A records pointing to previous hosts to avoid conflicts.
– Keep existing MX/DKIM/SPF/DMARC if your email is already working.
– Save and wait for propagation.

Back in WordPress.com:
– My Home > Domains > your domain > Make Primary when ready.
– SSL will provision when the domain resolves to WordPress.com’s IPs. Expect anywhere from a few minutes to several hours.

What About Subdomains?

– Subdomain to WordPress.com: Create a CNAME for blog.example.com pointing to your root domain (example.com) or as instructed by WordPress.com for subdomain mapping. Then add the subdomain in WordPress.com > Domains > Add subdomain.
– Subdomain to another service: Keep your apex (example.com) on WordPress.com, and point shop.example.com to your ecommerce provider (e.g., shops.myshopify.com) via CNAME. For apex on WordPress.com and various subdomains elsewhere, Option B often keeps things simpler.

Troubleshooting Common Issues

– Domain shows “Not found” or displays your registrar’s parking page: Your nameserver change or A/CNAME updates haven’t propagated yet, or old records are still present. Check with a global DNS checker (whatsmydns.net) and verify only the correct records remain.
– SSL pending or “Not secure”: Wait for propagation. Ensure the A/CNAME values match WordPress.com guidance and that there are no conflicting records. For nameserver changes, give it a few hours after the domain resolves.
– Redirect loops between www and non-www: Ensure only one canonical is set. On WordPress.com, choose your primary domain and avoid external redirects duplicating the behavior.
– Email stopped working after nameserver change: You forgot to re-add MX, SPF, and DKIM at the new DNS host. Add them exactly as your email provider specifies. Allow time to propagate.
– DNSSEC “SERVFAIL”: Remove stale DS records after moving nameservers. Re-enable DNSSEC later with the new provider’s DS values if supported.
– Using Cloudflare: If you must use Cloudflare, start with DNS-only (gray cloud) for the A and CNAME records to avoid SSL handshakes conflicting while you test. WordPress.com already includes performance/caching—doubling up can complicate things.

Best Practices That Save Headaches

– Keep both versions working: Add both root and www, then pick a primary in WordPress.com. The platform will 301 the non-primary to the primary.
– Set a sane TTL: 300–600 seconds while you’re making changes; increase later (e.g., 3600–14400) once stable.
– Document your old records: Before changing anything, export or screenshot your existing DNS. It’s the “undo” button you’ll wish you had.
– Secure email deliverability: SPF + DKIM + DMARC matter in 2024+ as mailbox providers crack down on spoofing. Even basic DMARC with p=none gives you reporting and visibility.
– Maintain brand consistency: If you’re using a newer TLD (like .zip or .mov), be extra mindful of user trust and phishing detection; many brands still prefer .com, .org, or strong ccTLDs for credibility and recognition.

Industry and Market Notes (2024–2026)

– Domain pricing trends: Wholesale .com pricing has climbed in recent years due to allowable increases, and many retail registrars passed these through. Consider multi-year renewals to lock rates if your budget is sensitive.
– Registrar shifts: Google Domains migrated to Squarespace Domains in 2023–2024, so UI and DNS features changed for many users. If your domain moved, double-check DNS settings and auto-renew.
– New TLDs and brand safety: Novel TLDs continue to launch and some gain traction (.ai, .dev, .app). They can be great for positioning, but weigh user trust and email deliverability; some security filters treat unfamiliar TLDs more cautiously.
– WordPress.com investments: WordPress.com has improved domain/DNS tooling and auto-SSL provisioning. If you register and host DNS at WordPress.com, day-2 admin (like adding MX or setting up DMARC) is straightforward from one dashboard.

Examples

Example 1: Simple brand site, no email yet
– Choose nameserver route.
– Change nameservers to ns1/ns2/ns3.wordpress.com.
– Wait for propagation; SSL appears automatically.
– Later, add Professional Email or Google Workspace. Add MX/DKIM/SPF in WordPress.com DNS.

Example 2: Business with existing email at Microsoft 365, plus a shop subdomain elsewhere
– Keep DNS at your current provider (Option B).
– Add A: @ -> 192.0.78.24 and 192.0.78.25.
– Add CNAME: www -> example.com.
– Leave MX/DKIM/SPF/DMARC as-is so email isn’t interrupted.
– Add CNAME: shop -> shops.myshopify.com (or as instructed).
– Set primary domain in WordPress.com; verify SSL.

Quick Glossary

– Nameservers: Tell the world which DNS server is authoritative for your domain (who has the records).
– A record: Maps a name to an IPv4 address (WordPress.com uses 192.0.78.24 and 192.0.78.25).
– CNAME: An alias that points one name to another (e.g., www to example.com).
– MX/SPF/DKIM/DMARC: Email routing and authentication records.
– DNSSEC: Security layer for DNS. Great when configured correctly; breaks things if DS records don’t match your DNS host.

Verification and Propagation: What’s Normal

DNS propagation is like traffic lights resetting across a city: it happens in stages, not all at once. What to expect:

– Local changes may appear in minutes; global consistency can take a few hours.
– SSL can lag behind DNS by a bit while certificates are issued.
– If things look off for more than 24 hours, re-check records, clear cache, and test from a different network.

Useful tools:
– whatsmydns.net: Quick global record checks.
– dig/nslookup: Precise command-line checks.
– Security headers checkers: Confirm HTTPS and HSTS if you’ve enabled it.

A Minimalist Checklist You Can Follow

– Add your domain in WordPress.com > Domains.
– Choose nameservers (simple) or A/CNAME (flexible).
– If changing nameservers, remove old DS records first if DNSSEC was enabled.
– Update nameservers or add A/CNAME records as instructed.
– Wait for propagation; confirm with a DNS checker.
– Set the primary domain in WordPress.com.
– Confirm SSL is active.
– If you use email, verify MX/DKIM/SPF/DMARC are correct at the active DNS host.
– Test the site and email from multiple locations.

Closing Thought

Connecting a custom domain to WordPress.com is mostly about making one good decision up front—nameservers vs. A/CNAME—and then following through carefully. Once it’s set, you’ll enjoy the benefits of a memorable domain, automatic SSL, and a setup that scales with you as your site and brand grow. Take it one step at a time, and you’ll go from “parked” to polished in an afternoon.