Firebase points both the root and www at the same address with A records — 199.36.158.100 — and asks for a TXT record to verify the domain, which must stay. Remove every record pointing at other hosts, or Firebase cannot issue the certificate.
The records to add
| Name | Type | Value |
|---|---|---|
@ | A | 199.36.158.100 |
www | A | 199.36.158.100 |
@ | TXT | The verification value Firebase shows (hosting-site=… in the advanced set-up) |
The Firebase console may also list an IPv6 (AAAA) record; add it as shown.
| Verification TXT | Keep it — Firebase says it must stay present |
| Certificate | Up to 24 hours after DNS points to Firebase |
Check your domain
Enter your domain: we look up its records and compare them with what Firebase Hosting expects — the root, www, and any record left over from before.
Step by step
- In the Firebase console, open Hosting and add the custom domain; Firebase shows the records to add.
- Add the TXT record to verify ownership, and the A records for the root and www.
- Remove any A, AAAA or CNAME records that point at other hosts.
- Wait for the status to go from Pending to Minting to Connected.
What to remove
- Any A or CNAME records pointing at other providers — Firebase says it cannot issue a certificate while they exist — and AAAA records not from Firebase.
The certificate
The certificate can take up to 24 hours after the records point to Firebase, and a certificate for another name may show briefly while it is issued. CAA records must allow letsencrypt.org and pki.goog.
Common mistakes
- Removing the verification TXT record after connecting.
- Leaving records for the old host beside Firebase’s.
Sources
Records checked on 26 September 2026 against these official sources:
- Connect a custom domain — firebase.google.com