DNS Configuration Errors

Struggling with DNS configuration for your custom domain? This guide covers the most common DNS setup problems, from record conflicts to propagation delays, helping you successfully connect your domain to Firebuzz.

Understanding DNS for Custom Domains

When you add a custom domain to Firebuzz, you must create a CNAME record at your DNS provider pointing to Firebuzz's infrastructure. This record tells the internet where to route traffic for your domain.

Troubleshooting

CNAME Record Not Found

Firebuzz verification cannot detect your CNAME record, even though you believe you added it correctly.

Solution:

1. Log in to your DNS provider (registrar, Cloudflare, Route53, etc.)
2. Navigate to DNS management or DNS records section
3. Verify a CNAME record exists for your subdomain
4. Check the record name is entered correctly:
   • For www.example.com, enter "www" (not the full domain)
   • For landing.example.com, enter "landing"
   • Don't include your root domain in the name field
5. Copy the target value exactly from Firebuzz (click the copy icon)
6. Ensure you clicked Save, Apply Changes, or Update Records
7. Wait 10-15 minutes for initial propagation
8. Test using dnschecker.org to verify the record exists
9. Return to Firebuzz and click Sync Status

Conflicting DNS Records

You added the CNAME record, but your DNS provider shows errors about conflicts or won't let you save the record.

DNS rules prohibit multiple record types for the same name. CNAME records cannot coexist with A, AAAA, or other CNAME records for the same subdomain.

Solution:

1. Check for existing A records pointing to your subdomain
2. Delete any A or AAAA records for the subdomain you're configuring
3. Remove any old or duplicate CNAME records for the same name
4. Verify only ONE CNAME record exists for your subdomain
5. Check for MX records on the subdomain (rare but can conflict)
6. Save changes and wait 5 minutes for cache clearing
7. Add the CNAME record from Firebuzz
8. Test with dnschecker.org after 10 minutes

DNS Propagation Taking Too Long

You configured DNS correctly, but changes aren't reflecting even after several hours. Verification remains pending in Firebuzz.

Solution:

1. Check the TTL (Time To Live) setting on your old record
2. High TTL values (3600+ seconds) cause slower propagation
3. Wait the full TTL duration for old records to expire from caches
4. Flush your local DNS cache:
   • Windows: Open Command Prompt and run ipconfig /flushdns
   • Mac: Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
   • Linux: Run sudo systemd-resolve --flush-caches
5. Test from a different device or network
6. Use whatsmydns.net to check global propagation
7. Some regions may show the new record while others still show old data
8. Wait up to 48 hours for full global propagation
9. For future changes, lower TTL to 300 seconds before making updates

Wrong DNS Provider Configuration

You're adding DNS records but they're not taking effect because you're editing in the wrong place.

Domain ownership and DNS management can be split between providers. Your domain might be registered at GoDaddy but have DNS managed by Cloudflare.

Solution:

1. Perform a WHOIS lookup on your domain using who.is
2. Look for "Name Server" entries in the WHOIS result
3. The nameserver company is where you must configure DNS
4. Common nameserver patterns:
   • ns1.cloudflare.com - Manage DNS in Cloudflare
   • ns1.digitalocean.com - Manage DNS in DigitalOcean
   • dns1.registrar-servers.com - Manage DNS at your registrar
5. If nameservers point to your registrar, edit DNS there
6. If nameservers point to a third-party DNS provider, edit there
7. Changes made at your registrar won't work if DNS is delegated elsewhere
8. Verify you're logged into the correct account at the correct provider

Subdomain vs Root Domain Confusion

You're unsure which DNS records to create for different domain configurations or what values to enter in the name field.

Solution:

Use this reference table for DNS configuration:

Important notes:

• For subdomains, enter only the subdomain part (before the first dot)
• Never enter your full domain in the name field for subdomains
• Root domain support requires CNAME flattening or ALIAS (provider-dependent)
• When in doubt, use www.example.com which works everywhere

DNS Provider Doesn't Support CNAME Flattening

You want to use your root domain (example.com without www) but your DNS provider won't accept a CNAME record at the root.

This is a technical limitation of DNS. Root domains can only have A records under standard DNS rules, but some modern providers support CNAME flattening or ALIAS records as a workaround.

Solution:

1. Check if your provider supports CNAME flattening or ALIAS records
2. Providers with support: Cloudflare, AWS Route53, DNSimple, NS1, Netlify DNS
3. If supported, create an ALIAS record instead of CNAME
4. Point the ALIAS to the target provided by Firebuzz
5. If not supported, use a subdomain instead: www.example.com
6. Configure domain forwarding from root to www:
   • Most registrars offer URL forwarding or domain redirect features
   • Forward example.com to www.example.com with 301 redirect
   • This gives visitors the impression of using the root domain
7. Consider migrating DNS to Cloudflare (free) for CNAME flattening support

Record Saving But Not Appearing in Verification

Your DNS provider shows the record saved successfully, but external DNS checkers and Firebuzz verification cannot find it.

Solution:

1. Verify the record type is CNAME (not A, AAAA, or TXT)
2. Check that you clicked Save, Apply, or Publish after adding the record
3. Some providers require explicit confirmation before changes go live
4. Look for a "pending changes" indicator in your DNS dashboard
5. Verify you have permission to edit DNS records for this domain
6. Check you're editing the correct domain if you manage multiple domains
7. Wait 15 minutes and check dnschecker.org again
8. Try deleting and re-creating the record
9. Contact your DNS provider's support if records won't persist

DNS Provider Interface Confusion

Your DNS provider's interface is confusing, and you're unsure where to enter the values from Firebuzz.

Solution:

Different providers use different terminology, but the concepts are the same:

Common field names:

• Name / Host / Hostname: Enter your subdomain (e.g., "www")
• Value / Target / Points To: Enter the value from Firebuzz
• Record Type / Type: Select CNAME
• TTL: Use default or 3600 (1 hour)

Provider-specific notes:

• GoDaddy: Name = subdomain, Value = target, Type = CNAME
• Namecheap: Host = subdomain, Value = target, Type = CNAME Record
• Cloudflare: Name = subdomain, Target = value, Proxy status = DNS only (gray cloud)
• Google Domains: Name = subdomain, Type = CNAME, Data = target

General tips:

1. Look for "Add Record" or "Create Record" button
2. Select CNAME from record type dropdown
3. Don't include "@" or your domain name in the subdomain field for subdomains
4. For root domain, use "@" or leave blank (provider dependent)

DNS Provider Guides

Cloudflare DNS Configuration

1. Log in to Cloudflare and select your domain
2. Go to DNS in the left sidebar
3. Click Add record
4. Select CNAME from the Type dropdown
5. Name: Enter your subdomain (e.g., "www")
6. Target: Paste the value from Firebuzz
7. Proxy status: Click the cloud icon to gray (DNS only)
8. TTL: Auto
9. Click Save

Common DNS Provider Interfaces

GoDaddy:

1. Go to My Products > Domains
2. Click DNS next to your domain
3. Scroll to Records section
4. Click Add > CNAME
5. Fill in Name and Value

Namecheap:

1. Domain List > Manage > Advanced DNS
2. Host Records section
3. Add New Record > CNAME Record
4. Fill in Host and Value

AWS Route53:

1. Hosted Zones > Select your domain
2. Create Record
3. Record name: subdomain
4. Record type: CNAME
5. Value: target from Firebuzz

Verification Steps

After configuring DNS, follow these steps to verify and troubleshoot:

1. Wait at least 10 minutes for initial propagation
2. Test using dnschecker.org:
   • Enter your full subdomain (www.example.com)
   • Select CNAME from dropdown
   • Check results from multiple locations
3. Verify the CNAME target matches what Firebuzz provided exactly
4. Return to Firebuzz and click Sync Status
5. If still pending, wait another 15 minutes and try again
6. After 2 hours, double-check your DNS configuration
7. After 48 hours, remove and re-add the domain for a fresh start

FAQ

Related Resources

• Domain Not Connecting
• SSL Certificate Errors
• Adding Custom Domains