Custom-domain verification in Firebase Auth doesn't propagate

Authentication
,
1

It has been days now and I’ve been trying to verify the Custom domain for email templates service so the verification emails and password resets goes from my custom domain.

The instructions from Firebase are two TXT and two CNAME records. Domain is on NameCheap and I tried adding it for both domain. com and for www domain .com but it doesn’t propagate. I tried host @ for apex domain and www host for subdomain.

Also both root and subdomain are verified for hosting and working fine, but these auth templates are just not propagating…

Did anyone else face this issue? I would really appreciate any help.

2

Here’s what might help with your Firebase custom domain TXT and CNAME verification issues on NameCheap:

  1. For the TXT records, add them exactly as Firebase specifies, usually with the host as “@” for the root domain and “www” for the subdomain.
  2. For CNAME records, also ensure you use the correct hosts Firebase gave, matching either the apex or www subdomain.
  3. DNS changes usually take some time to propagate—sometimes up to 48 hours; double-check with a tool like WhatsMyDNS to see if records show up globally.
  4. Sometimes NameCheap’s dashboard needs you to save and confirm changes explicitly—make sure it’s fully saved and active.
  5. Since your root and www hosting is verified but auth templates aren’t propagating, double-check Firebase’s exact record entries; any typo or extra spaces can cause failure.

If you want, I can help you verify the exact record values and hosts you should put in NameCheap. Want me to check that? :blush:

Here’s what I see from your Firebase DNS records screenshot:

  1. For the two TXT records,

    • Use host: @
    • Values look like Firebase verification TXT strings, looks correct.

  2. For the CNAMEs,

    • One uses host: __gtemp4._domainkey pointing to a Firebase address. Correct!
    • The other uses host: power2heal.com which should NOT be the host; it should be something like www or another subdomain, not the root domain itself for CNAME.

You should:

  • Remove the CNAME with host power2heal.com (that’s invalid).
  • Add CNAME with host www (or whatever Firebase specifies) pointing to the required Firebase address.

This mismatch often blocks propagation. Also, give it 24-48 hrs for DNS to update fully.

Need help updating that CNAME. Looks good! For your CNAME records, keep __gtemp4._domainkey pointing to Firebase as is, but replace the CNAME with host power2heal.com by one with host www pointing to the Firebase target they gave you.

Also, make sure your TXT records have host @ and their exact values from Firebase.

Give DNS up to 48 hours to fully propagate. Need a hand crafting the exact CNAME record text to add? :blush:

3

I used dig to fix it. Thanks