Domain Not Connecting

Your custom domain isn't connecting to Firebuzz? This guide covers the most common connection and verification issues, helping you diagnose why your domain shows pending or failed status and how to fix it.

Understanding Domain Connection

When you add a custom domain to Firebuzz, the platform verifies ownership through DNS records. Connection issues typically stem from DNS misconfiguration, propagation delays, or provider-specific limitations.

Troubleshooting

Domain Status Shows Pending

Your domain was added to Firebuzz but remains in pending verification status, preventing you from publishing landing pages to it.

Solution:

1. Navigate to Brand then Domains
2. Click Configure on your pending domain
3. Copy the CNAME record Name and Value exactly as shown
4. Log in to your domain registrar or DNS provider (GoDaddy, Namecheap, Cloudflare, etc.)
5. Add a new CNAME record with the copied values
6. Save your DNS configuration changes
7. Return to Firebuzz and click Sync Status
8. Wait 10-15 minutes and check again if still pending

Wrong CNAME Configuration

Your DNS records are configured but verification repeatedly fails, or DNS checkers show incorrect values.

Solution:

1. Verify you created a CNAME record (not an A, AAAA, or TXT record)
2. Copy values directly from Firebuzz using the copy button to avoid typos
3. Check for trailing dots or extra spaces in the record value
4. For subdomain www.example.com, enter only "www" in the Name field (not the full domain)
5. For root domains, check if your provider requires "@" or blank in the Name field
6. Remove any conflicting A records for the same subdomain
7. Test your configuration using dnschecker.org
8. Wait 15 minutes after making corrections, then click Sync Status

Domain Shows Failed Status

Verification failed after multiple attempts, and the domain status changed from pending to failed.

Solution:

1. Click Remove to delete the failed domain
2. Log in to your DNS provider and delete any old CNAME records for this subdomain
3. Wait 5 minutes for cache clearing
4. Add the domain again in Firebuzz
5. Configure the new CNAME records provided
6. Verify ownership of the domain with your registrar
7. Check that no A records conflict with your CNAME
8. Use whatsmydns.net to verify global DNS propagation

Using Root Domain Without Subdomain

You want to use example.com instead of www.example.com but standard CNAME configuration isn't working.

Root domains (apex domains) have special DNS requirements that not all providers support. Standard CNAME records don't work at the root level due to DNS specifications.

Solution:

1. Check if your DNS provider supports CNAME flattening or ALIAS records
2. Providers with support: Cloudflare, AWS Route53, DNSimple, NS1
3. If supported, create an ALIAS or flattened CNAME record pointing to the Firebuzz value
4. If not supported, use www.example.com instead
5. Configure a redirect from example.com to www.example.com at your registrar
6. Most registrars offer URL forwarding or domain forwarding features

Multiple Domains With Mixed Status

You added several custom domains to your project, but only some show active status while others remain pending or failed.

Solution:

1. Review each domain card individually in Domains
2. Each domain requires separate DNS configuration at its respective registrar
3. If domains are registered at different providers, configure each one separately
4. Verify you're viewing the correct project (domains are project-specific)
5. Check that each domain has unique CNAME records (no duplicates)
6. Test each domain independently using dnschecker.org

DNS Provider Not Saving Records

You add the CNAME record at your DNS provider, but it doesn't appear or disappears after saving.

Solution:

1. Ensure you clicked Save, Apply, or Update Changes after adding the record
2. Some providers require explicit confirmation before saving DNS changes
3. Check that your account has permission to edit DNS records
4. Verify you're editing the correct domain (not a different domain in your account)
5. Contact your DNS provider's support if records won't save
6. Consider migrating DNS management to Cloudflare for easier configuration

Verifying Domain Status

In Firebuzz

1. Go to Brand then Domains
2. Check the status badge on each domain card:
   • Pending: Awaiting DNS verification
   • Active: Successfully connected
   • Failed: Verification failed
3. Click Sync Status to force an immediate check

Using External Tools

Test DNS propagation and configuration using these third-party tools:

• dnschecker.org - Check DNS propagation across multiple locations
• whatsmydns.net - Global DNS propagation checker with visual map
• mxtoolbox.com/SuperTool.aspx - Comprehensive DNS lookup tool

FAQ

Related Resources

• Adding Custom Domains
• DNS Configuration Errors
• SSL Certificate Errors