--- title: "Framer Custom Domain: Setup and Troubleshooting" description: "How to connect a custom domain to a Framer site, the DNS records involved, and how to fix the most common connection and SSL problems." canonical_url: "https://framerhub.io/blog/framer-custom-domain-guide" last_updated: "2026-09-29T00:00:00.000Z" --- Connecting a **framer custom domain** is usually a five-minute task that occasionally turns into an hour of confusion over DNS records and SSL errors. The process itself is simple; the confusion almost always comes from either DNS propagation delay or a leftover conflicting record from wherever the domain lived before. This guide covers the setup step by step and the specific fixes for the errors people run into most often. --- ## Before you start: what you need - **A registered domain** from any registrar (GoDaddy, Namecheap, Google Domains, Cloudflare, or others). Framer doesn't require you to register or transfer your domain to them. - **Access to your domain's DNS settings** at whichever registrar or DNS provider manages it. If you're not sure who manages DNS for a domain, checking the registrar you purchased it from is the usual starting point. - **Your Framer site's domain connection values**, found in your site's domain settings inside Framer, which provide the exact CNAME and A record targets for your specific project. --- ## Setting up a custom domain, step by step 1. **Open your Framer project's domain settings** and choose to add a custom domain. 2. **Enter your domain name** (either the root domain, like yoursite.com, or a subdomain, like [www.yoursite.com](http://www.yoursite.com)). 3. **Copy the DNS record values Framer provides.** This is typically a CNAME target for a subdomain, and an A record (or ALIAS/ANAME) value for the root domain. 4. **Log in to your domain registrar or DNS provider's dashboard** and navigate to DNS management for your domain. 5. **Add the records exactly as provided**, matching record type, name/host, and value precisely. A common mistake here is a typo in the target value or using the wrong record type. 6. **Remove any conflicting existing records** for the same host (an old A record pointing to a previous host, for example), since conflicting records for the same name commonly cause connection failures. 7. **Save your DNS changes and wait for propagation.** This can take a few minutes to 48 hours, though a few hours is typical. 8. **Confirm the domain is connected in Framer's dashboard**, and check that an SSL certificate has been issued once DNS is confirmed correctly pointing to Framer. --- ## Root domain vs. subdomain: what's different **Subdomains** ([www.yoursite.com](http://www.yoursite.com), blog.yoursite.com) generally only need a CNAME record, which is straightforward since CNAME records are designed for exactly this: pointing one hostname to another. **Root/apex domains** (yoursite.com with no prefix) can't technically use a CNAME record under standard DNS rules, since the root of a domain has other required records (like MX for email) that can't coexist with a CNAME at that same level. Instead, root domains typically use an A record pointing to a specific IP, or an ALIAS/ANAME record if your DNS provider supports it, which behaves like a CNAME but is valid at the root level. **Common pattern:** connect the root domain with an A record (or ALIAS) and redirect www to the root (or vice versa) with a CNAME plus a redirect rule, so visitors land on your intended version regardless of which they type. --- ## Troubleshooting the most common problems ### SSL certificate errors or "not secure" warnings This is almost always one of two things: DNS hasn't fully propagated yet (wait longer, and re-check), or the certificate is still being issued (which typically happens automatically shortly after DNS resolves correctly). If it's been more than a few hours past confirmed DNS propagation with no certificate, double-check the DNS records match exactly what Framer provided, then verify again from your domain settings. ### Domain shows a "not connected" or pending status Usually means DNS records haven't propagated yet, or there's a typo in the record value. Use a DNS lookup tool to confirm what's actually resolving publicly for your domain, comparing it against the exact value Framer's domain settings specify. ### Old site or a parking page still showing This typically means a cached DNS response (yours or a visitor's browser/ISP cache) hasn't updated yet, or there's a conflicting record still present pointing to the old host. Clear your own DNS cache locally, and confirm no old A or CNAME records remain at your DNS provider for the same hostname. ### www works but the root domain doesn't (or vice versa) This usually means only one of the two required record types was set up. Root domains need their own record (A/ALIAS) separate from the www subdomain's CNAME; missing one leaves that version of the domain unconnected. ### Email stops working after connecting a domain If your domain has email hosted elsewhere (Google Workspace, Microsoft 365, etc.), make sure you haven't accidentally removed the MX records while adding Framer's records. MX records for email are independent of the A/CNAME records used for your website and should be left untouched. --- ## DNS propagation: what to expect DNS changes don't take effect instantly everywhere. Different DNS resolvers around the world cache records for varying lengths of time (determined by the record's TTL, time-to-live setting), which is why propagation can take anywhere from a few minutes to 48 hours depending on your specific DNS provider and any previous record's TTL. This is normal and not a sign that something is broken. The most common mistake during this window is repeatedly changing DNS records while troubleshooting, which can actually extend the effective propagation time by introducing new values before the previous change has fully settled everywhere. Make your changes once, verify them carefully for typos before saving, and then wait rather than iterating rapidly. **Practical tips:** - **Lower your TTL before making changes** if your DNS provider allows it, so future changes propagate faster. - **Use a public DNS lookup tool** to check what's actually resolving from different locations, rather than only checking from your own device, which may have a cached result. - **Be patient past the first hour.** Most connections resolve within a few hours, but occasional edge cases (particular ISPs, particular resolvers) take longer. --- ## Redirecting a secondary or old domain Some projects need more than one domain pointed at the same Framer site, a secondary domain purchased for brand protection, or an old domain being retired in favor of a new one. **For an old domain being fully retired**, set up a redirect at the domain/registrar level (or through a redirect service) pointing to your new domain, rather than leaving the old one connected to Framer or, worse, pointing nowhere. This preserves any direct traffic and bookmarks still hitting the old address. **For a secondary domain meant to always point to the same site** (a `.net` purchased alongside a primary `.com`, for example), a straightforward domain forward/redirect at the registrar level to your primary domain is usually simpler than trying to connect both domains directly to the same Framer project. **Avoid running the exact same content live on two separately connected domains without a canonical redirect.** Search engines can treat this as duplicate content, which dilutes ranking signals that would otherwise consolidate on one domain. --- ## A pre-launch domain checklist - [ ] DNS records match exactly what Framer's domain settings specify (record type, host, value) - [ ] No conflicting old records remain from a previous host - [ ] Both root domain and www (or your chosen canonical version) resolve correctly, with the non-canonical version redirecting - [ ] SSL certificate is issued and the site loads without a security warning - [ ] Email (MX records) still functions correctly if hosted separately from your website - [ ] Any old domain being retired has a redirect in place rather than being left disconnected - [ ] Sitemap and any external references (social profiles, business listings) point to the final, canonical domain --- ## Domain setup and SEO Connecting a custom domain correctly matters beyond just making the site accessible; it affects how search engines see your site too. **Pick one canonical version and stick to it.** Decide whether www or the root domain is your primary version, redirect the other to it, and use that version consistently in your sitemap, internal links, and any external references (social profiles, business listings). **If migrating from an existing domain or site**, make sure old URLs redirect properly to their new equivalents rather than returning errors, to preserve any accumulated search ranking value. For the fuller picture of technical SEO considerations for a Framer site, see our [Framer SEO guide](/blog/framer-seo-guide). Once your domain is live and correctly configured, it's a good moment to review the rest of your site's setup, plugins, forms, and CMS structure, since a fresh domain connection is often part of a broader launch. Browse the [FramerHub plugin catalog](/plugins) if you're finishing up other parts of the build at the same time, and check our [performance guide](/blog/optimize-framer-site-performance) to make sure your newly live domain is also serving a genuinely fast site. --- ## FAQ ### What DNS records do I need to connect a custom domain to Framer? Typically a CNAME record for a subdomain (like www) pointing to the value Framer provides, and either an A record or ALIAS/ANAME record for the root/apex domain, since apex domains can't use a CNAME per standard DNS rules. Exact values are provided in Framer's own domain settings for your specific site. ### How long does it take for a custom domain to work on Framer? DNS changes can take anywhere from a few minutes to 48 hours to fully propagate, though most changes are visible within a few hours. SSL certificate issuance for the new domain typically follows shortly after DNS propagates correctly, adding a short additional delay before the site is fully secure and live. ### Why is my Framer custom domain showing an SSL error? This usually means DNS hasn't fully propagated yet, or a certificate is still being issued. It can also happen if DNS records point to the wrong target, or if there's a conflicting record (like an old A record from a previous host) still present at your DNS provider that needs to be removed. ### Can I use a subdomain instead of the root domain with Framer? Yes. Connecting a subdomain (like blog.yoursite.com) generally only requires a CNAME record pointing to Framer's provided value, which is simpler than root domain setup since it avoids the apex domain CNAME restriction entirely. ### Do I need to change my domain registrar to use Framer? No. You keep your domain registered wherever you originally purchased it (GoDaddy, Namecheap, Google Domains, etc.) and only update the DNS records at that registrar (or your DNS provider) to point to Framer. There's no need to transfer domain registration itself. --- ## Bottom line Connecting a **framer custom domain** is a straightforward DNS task that mostly goes wrong for two reasons: propagation delay (which just needs patience) or a conflicting old record left over from a previous host (which needs a manual cleanup). Match the record types Framer provides exactly, remove anything conflicting, and give it a few hours before troubleshooting further. For the broader technical setup that matters once your domain is live, canonical URLs, redirects, and sitemap configuration, see our [Framer SEO guide](/blog/framer-seo-guide). *Last updated: September 2026*