Framer Custom Domain Not Connecting? DNS Fixes

Why won’t my custom domain connect to Framer?

Your custom domain won’t connect most often because the DNS records at your registrar don’t match what Framer requires, or because a conflicting old record (a previous A record or a parked-domain redirect) is overriding the new one. Framer tells you the exact records to add; the domain connects once those are in place and propagated, and stays broken while there’s a mismatch.

The mental model: Framer doesn’t control your domain’s DNS — your registrar (GoDaddy, Namecheap, Cloudflare, Google Domains, etc.) does. Connecting the domain means going to your registrar and pointing it at Framer with the right records. Most failures are a wrong, missing, or conflicting record there.

What DNS records does Framer need?

Framer needs an A record for a root/apex domain (like example.com) pointing to Framer’s IP, and a CNAME record for a subdomain (like www.example.com) pointing to Framer’s host — the exact values are shown in your Framer domain settings, and you must copy them precisely. In practice:

• Root domain (example.com) → add the A record(s) Framer specifies, pointing to its IP address.

• Subdomain (www.example.com) → add a CNAME record pointing to the host Framer specifies.

• Both → many setups connect www and redirect the root to it (or vice versa); follow the exact pairing Framer shows for your case.

Copy the values verbatim from Framer’s domain settings — a single wrong character means the domain won’t resolve. Add them at your registrar’s DNS management page, save, and wait for propagation.

Why is my domain connected but still not working?

If you’ve added the records but the domain still doesn’t work, it’s almost always DNS propagation (which can take from minutes up to 48 hours) or a leftover conflicting record fighting the new one — both are common and both resolve. DNS changes aren’t instant; they roll out across the internet gradually.

To diagnose: use a DNS-checker tool to see whether your new records have propagated globally, and check your registrar for old records (a previous A record from a prior host, a parked-domain forward, or a conflicting CNAME) that need deleting. A stale record silently overriding the new one is a classic cause of “I added everything and it still doesn’t work.”

How long does DNS propagation take for a Framer domain?

DNS propagation for a Framer domain usually completes within a few minutes to a couple of hours, but can take up to 48 hours depending on your registrar and the record’s TTL — if it’s been under 48 hours and your records are correct, the fix is often just to wait. Lowering the TTL before making changes can speed future updates, but for a one-time connection, patience is usually the answer.

Don’t repeatedly change the records while waiting — that resets the clock. Set them correctly once, confirm with a DNS checker, and give it time.

Why is my Framer domain showing an SSL or “not secure” error?

An SSL or “not secure” error right after connecting usually means the certificate hasn’t finished provisioning yet — Framer issues SSL automatically once DNS is verified, and it can take a short while after the domain connects for HTTPS to go live. This typically resolves on its own within a few hours of the domain connecting correctly.

If the SSL error persists well after the domain resolves, it’s usually a lingering DNS issue (a conflicting record, or the domain not fully verified on Framer’s side). Recheck that your records exactly match Framer’s, remove conflicts, and confirm the domain shows as connected in Framer’s settings — SSL follows a clean DNS setup.

FAQ: Framer custom domain not connecting

Why won’t my custom domain connect to Framer? Usually the DNS records at your registrar don’t match what Framer requires, or a conflicting old record is overriding the new one. Copy Framer’s exact A and CNAME values to your registrar and remove any stale records.

What DNS records do I need for Framer? An A record for a root domain (example.com) pointing to Framer’s IP, and a CNAME for a subdomain (www) pointing to Framer’s host. The exact values are in your Framer domain settings — copy them precisely.

How long does it take for a Framer domain to connect? DNS propagation usually takes minutes to a couple of hours, up to 48 hours in some cases. If your records are correct and it’s been under 48 hours, waiting is often the fix.

Why does my Framer domain say “not secure”? The SSL certificate hasn’t finished provisioning. Framer issues SSL automatically once DNS is verified; it usually resolves within a few hours of the domain connecting. Persistent errors point to a DNS conflict.

I added the records but my domain still doesn’t work — why? Either DNS hasn’t propagated yet, or an old conflicting record (a previous A record or parked-domain forward) is overriding the new one. Use a DNS checker and remove stale records at your registrar.

Where do I change DNS records for a Framer domain? At your domain registrar (GoDaddy, Namecheap, Cloudflare, etc.), not in Framer. Framer tells you which records to add; you add them in your registrar’s DNS management settings.

Want your Framer site launched without the domain headaches?

FramerLab handles the full launch — build, domain, DNS, SSL, and (for migrations) redirects — so your site goes live cleanly. Senior-led, NDA-friendly.Book a discovery call.

• Start at theFramerLab

• Our full process: Our Framer website process

• Not indexed either? Framer site not showing on Google

• Migrating?Webflow → Framer migration

Written by Dilip, founder of FramerLab, with 5+ years designing and building on Framer. Connect onLinkedInandX.