Bird
0
0

You set a CNAME record pointing your custom domain to ghs.googlehosted.com but your site still doesn't load. What should you check next?

medium📝 Debug Q7 of 15
GCP - Cloud Run
You set a CNAME record pointing your custom domain to ghs.googlehosted.com but your site still doesn't load. What should you check next?
AChange the CNAME to an A record pointing to Google IPs
BDisable SSL for the custom domain
CDelete the CNAME and use MX records instead
DVerify that the domain is added and verified in GCP domain mappings
Step-by-Step Solution
Solution:

  1. Step 1: Confirm DNS record correctness

    CNAME to ghs.googlehosted.com is correct for App Engine custom domains.

  2. Step 2: Check domain mapping and verification

    The domain must be added and verified in GCP for it to work.

  3. Final Answer:

    Verify that the domain is added and verified in GCP domain mappings -> Option D

  4. Quick Check:

    Domain must be verified and mapped in GCP [OK]
Quick Trick: DNS correct? Then verify domain mapping in GCP [OK]
Common Mistakes:
  • Switching record types unnecessarily
  • Using MX records for website
  • Disabling SSL without cause

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More GCP Quizzes
Cloud Functions - Cloud Functions generations (1st vs 2nd) - Quiz 7medium Cloud Functions - Cloud Functions pricing - Quiz 7medium Cloud IAM Advanced - Access Context Manager - Quiz 3easy Cloud IAM Advanced - Data access logs - Quiz 10hard Cloud Load Balancing - URL maps for routing - Quiz 6medium Cloud Load Balancing - HTTP(S) Load Balancer (Layer 7) - Quiz 11easy Cloud Monitoring and Logging - Cloud Trace for latency analysis - Quiz 8hard Cloud Run - Cloud Run service concept - Quiz 7medium Cloud Run - Request-based auto scaling - Quiz 4medium Cloud SQL and Databases - Cloud SQL pricing - Quiz 9hard