Disconnect a custom domain
If you’re replacing this domain with a new one, disconnect the current domain first. Kajabi only issues new nameservers after the previous domain has been removed. While you’re between domains, your site stays live on its Kajabi subdomain (for example, yoursite.mykajabi.com). To finish the switch, see Reconnect or add a custom domain below.- From the Dashboard, go to Settings.
- Under Site settings, click Domain.
- In Site Domain Settings, click the more options (⋯) menu next to the custom domain you want to disconnect.
- Select Remove to complete the process.
Reconnect or add a custom domain
If you already have a custom domain connected and want to switch to a new one, disconnect the existing domain first. See Disconnect a custom domain above.- From the Dashboard, go to Settings.
- Under Site settings, click Domain.
- Click Setup Custom Domain.
- Choose and follow one of the available methods:
- Connect Domain to Kajabi (Nameserver Method): Update the nameservers at your domain registrar as provided by Kajabi.
- Subdomain Method: Update specific DNS records (e.g., CNAME) at your registrar per Kajabi’s instructions.
- Allow up to 24-48 hours for DNS propagation.
- Use CNAME when connecting a subdomain (e.g. courses.yourdomain.com), or when you cannot change name servers.
- Use nameservers for root domain connections.
Note: Once you switch to Kajabi’s nameservers, DNS management for your domain moves to Kajabi. You will no longer be able to add or edit DNS records at your registrar — all record changes must be made inside Kajabi under Settings > Site settings > Domain > [your domain] > DNS Settings.
Understanding domain connection status
After updating your nameservers, your domain will move through these states in Kajabi’s Domain settings:Note: If the Status is Pending or Failed after 72 hours, contact Kajabi Support. This indicates a backend sync issue that can’t be resolved by re-doing the setup steps.
Switch back to the Kajabi subdomain
If you want to use the default Kajabi subdomain instead of your custom domain:- From the Dashboard, go to Settings.
- Under Site settings, click Domain.
- Click the more options (…) menu next to your custom domain.
- Select Remove. This will automatically revert your Kajabi site to the default subdomain.
Troubleshoot common domain issues
Update DNS settings for specific registrars
Registrar interfaces change over time, so rather than walk through exact click-paths here, refer to each registrar’s own current documentation for the most accurate steps:- GoDaddy: Change my domain nameservers
- Squarespace: Disconnecting a third-party domain and Making changes to nameservers
- Namecheap: How to Change DNS For a Domain
- Porkbun: How to Change Nameservers
- Bluehost: How to Navigate the Nameservers Tab in Bluehost Portal
Note: These registrar guides only cover disconnecting your domain or changing its nameservers on their end. Once that’s done, complete Kajabi’s own setup under Reconnect or add a custom domain above to finish pointing the domain to Kajabi.
Member pages (login, library) return 404 or blank on a custom domain
If your homepage loads correctly at your custom domain but members see a 404 or blank page when trying to log in or access their library, the cause is usually not a DNS problem — the domain is connected. The more likely cause is the member’s browser blocking third-party cookies on your custom domain. Kajabi sets authentication cookies on your custom domain when members log in. If the browser or an extension blocks those cookies, the session can’t be established and the member sees a 404 or is redirected. Ask the member to test with this quick diagnostic: Open the login URL in an incognito or private window. If it works there, the issue is browser-side (extension or cookie settings), not a domain issue. For the full browser-side troubleshooting steps, point the member to: Resolve login issues across platforms. If the issue persists on both the custom domain AND the .mykajabi.com subdomain, then it is a domain configuration issue — follow the DNS troubleshooting steps above or contact Kajabi Support.Set up email DNS records (MX, SPF, DKIM, DMARC)
If you use a third-party email provider (Google Workspace, Microsoft 365, etc.) with your custom domain, you must manually add your email DNS records in Kajabi after switching nameservers. When you change nameservers, DNS authority transfers to Kajabi/Cloudflare — your registrar no longer controls DNS, so your old email records won’t carry over automatically. To add email DNS records in Kajabi:- From the Dashboard, go to Settings.
- Under Site settings, click Domain, then next to the gear icon, DNS Settings
- Click +Custom Record and select the type of record you need to add MX, TXT (SPF, DKIM, and DMARC) and CNAME records.
- Contact your email provider for the exact record values - Google Workspace: Set up MX records for Google Workspace, Microsoft 365: Connect your domain by adding DNS records.
Cloudflare Error 1014 (CNAME Cross-User Banned)
This error means a DNS record on your domain is pointing to a Kajabi-hosted site that belongs to a different Cloudflare account. It cannot be resolved without backend intervention. To resolve:- Do not attempt to re-add or reconfigure your domain — this will not fix a 1014 error.
- Contact Kajabi Support and include:
- Your full domain name (e.g., courses.yourdomain.com)
- Your domain registrar (e.g., GoDaddy, Namecheap)
- A screenshot of the error
- Whether this domain was previously connected to another Kajabi account
- Kajabi Support will coordinate with Cloudflare to release the cross-account lock.
FAQs
Why do my marketing emails show a kjbm address?
kjbm is a sending subdomain Kajabi uses exclusively for marketing email, so your Kajabi records never collide with the SPF, DKIM, DMARC, and MX records your webmail provider already has on your root domain. It’s a required part of connecting a custom email domain and can’t be removed or renamed.
If you’re troubleshooting DNS after a nameserver switch, note that these records live under kjbm.yourdomain.com, not your root domain — adding them at the root is the most common cause of a verification loop.
For the full explanation of why the subdomain is required and how to enable Strict DMARC, see Custom email domain requirements.