Firebase Hosting切换AWS Route53域名配置失效，求解决方法

Hey there, let's work through this TXT record issue for your Firebase Hosting domain switch. Since you've already got your Route 53 domain approved and added the record, here's a step-by-step breakdown of the most likely fixes to get Firebase to recognize it:

• Double-check every detail of your TXT record matches exactly
  Head back to your Firebase Console > Hosting > Custom Domains page, and copy the full TXT verification value (including the firebase-verification= prefix—don’t skip any characters!). Then in Route 53’s hosted zone:

  • Name field: For your root domain (e.g., example.com), use @. For a subdomain (e.g., app.example.com), just enter the subdomain part (app).
  • Type field: Make sure it’s set to TXT (not CNAME, A, or anything else).
  • Value field: Paste the full Firebase string directly. If there are spaces or special characters, wrap it in quotes (though Firebase’s verification strings are usually continuous, so this might not be necessary—but better safe than sorry). Avoid extra spaces or line breaks here.
  • TTL: Leave it at the default 300 seconds; no need to crank it up.

• Wait for DNS propagation (it’s not instant!)
  DNS records don’t update across the globe immediately. Even with a short TTL, it can take 10-30 minutes (and occasionally a few hours) for caches to refresh. To check if your record is live, run these commands in your terminal:

  nslookup -type=TXT your-domain.com
  # Or use dig for more detail
  dig TXT your-domain.com
  

  If the output includes your Firebase verification string, propagation is done.

• Confirm your Route 53 hosted zone is linked to your domain
  If you registered your domain through Route 53, this is usually automatic—but if you used another registrar, double-check that your domain’s DNS servers are set to the 4 name servers listed in your Route 53 hosted zone details. A mismatch here means Route 53’s records aren’t even being used for your domain.

• Manually trigger Firebase’s verification check
  Go back to the Firebase Custom Domains page and look for a "Reverify" button (or refresh the page if it’s stuck on "Verifying"). Sometimes Firebase’s automatic check has a delay, and manually triggering it can kickstart the process.

• Check for conflicting DNS records
  Make sure there aren’t other TXT records with the same name (e.g., old verification records for other services). Multiple TXT records for the same domain can cause Firebase to miss the one it needs. Temporarily remove any unrelated TXT records, verify, then add them back later.

• Rule out subdomain/CDN edge cases
  If you’re using a subdomain (like www.your-domain.com), ensure you didn’t enter the full domain in the Route 53 Name field (just the subdomain part, e.g., www). Also, if you’re using a CDN (like Cloudflare) in front of Route 53, make sure the CDN isn’t caching old DNS data—flush its cache or sync its DNS settings with Route 53.

内容的提问来源于stack exchange，提问作者Karo A