Custom Domains

Flint allows you to publish your entire site to your root domain (e.g., example.com). This is ideal when you want Flint to power your whole marketing website.

For hosting pages on a subdomain (e.g., pages.example.com), see Subdomains instead.

To connect your root domain to Flint, go to your site settings in the Flint dashboard and navigate to the "Domain" section. Toggle on "Use Custom Domain" and enter your domain (e.g., example.com).

Click the "Connect via Entri" button and follow the prompts. Entri will automatically configure your DNS records with supported domain registrars, no manual steps required. This is the fastest and easiest way to get your domain connected.

If you prefer to configure DNS manually, or if your registrar isn't supported by Entri:

1. 1.Copy the A record and TXT record details provided in the Flint dashboard
2. 2.Log in to your domain registrar's DNS settings
3. 3.Add the A record pointing your root domain to the IP address provided
4. 4.Add the TXT record for verification
5. 5.Save your changes and wait for DNS propagation (usually 15-30 minutes, sometimes up to 48 hours)

Different DNS providers use different conventions for the A record name when targeting your root domain:

• •Most providers: Use @ as the name
• •Cloudflare: Leave the name field blank, or enter your apex domain (e.g., example.com)
• •Some providers: Use the full domain name (e.g., example.com)

If you're unsure which format your provider uses, check their documentation or try @ first—it's the most common convention.

We recommend also setting up a redirect from www.example.com to example.com (or vice versa) for a consistent user experience. Most DNS providers offer this as a redirect rule or you can add a CNAME record for www pointing to your root domain.

To confirm your domain is working:

1. 1.Check the domain status in your Flint dashboard - it should show as "Connected"
2. 2.Visit your domain in a browser (e.g., https://example.com)
3. 3.Verify that your published pages load correctly
4. 4.Check that the SSL certificate is valid (look for the padlock icon)

If you see errors, double-check your DNS settings and wait for full propagation.

Flint automatically provisions SSL certificates for your domain once DNS is properly configured. This means your pages will be served over HTTPS with no additional setup required.

SSL provisioning typically completes within a few minutes after DNS propagation.

1. 1.DNS not propagating: Use a tool like dnschecker.org to verify your records are live globally. Some registrars have longer propagation times.

2. 2.SSL errors: Ensure DNS is fully propagated before expecting SSL to work. Clear your browser cache or try an incognito window.

3. 3.Cloudflare users: If using Cloudflare's proxy, you may need to configure SSL settings to "Full" mode in your Cloudflare dashboard.

4. 4.A record not working: Double-check the name field—try @, leaving it blank, or using your full domain depending on your provider.