Custom domains in GCP - Commands & Configuration

Introduction

Custom domains let you use your own website name instead of a default address. This makes your site easier to find and looks more professional. It solves the problem of having a long or unclear web address.

When you want your website to have a simple, memorable address like www.myapp.com instead of a long Google Cloud URL.

When you want to build trust with visitors by showing your own brand name in the web address.

When you need to connect your domain bought from a registrar to your Google Cloud service.

When you want to use HTTPS with your own domain for secure connections.

When you want to manage your website's address settings in one place.

Commands

This command connects your custom domain www.myapp.com to your Google App Engine app and sets up automatic SSL certificates for secure HTTPS.

Terminal

gcloud app domain-mappings create www.myapp.com --certificate-management=automatic

Expected Output

Created domain mapping [www.myapp.com].

Certificate management set to automatic.

→

--certificate-management=automatic - Automatically provisions and renews SSL certificates for HTTPS.

This command lists all custom domains currently connected to your Google App Engine app to verify the domain mapping.

Terminal

gcloud app domain-mappings list

Expected Output

DOMAIN NAME    SSL STATUS

www.myapp.com  managed

This command checks the DNS records for your custom domain to ensure it points to Google Cloud's servers.

Terminal

nslookup www.myapp.com

Expected Output

Server:  8.8.8.8

Address: 8.8.8.8#53



Non-authoritative answer:

www.myapp.com canonical name = ghs.googlehosted.com.

Key Concept

If you remember nothing else from this pattern, remember: connecting your custom domain to Google Cloud requires domain mapping and DNS setup to make your site reachable and secure.

Common Mistakes

Not updating DNS records at the domain registrar after creating the domain mapping.

Without correct DNS records, the domain won't point to your Google Cloud app, so visitors can't reach your site.

After creating the domain mapping, update your domain's DNS settings to point to Google Cloud as instructed.

Skipping the SSL certificate setup or using manual certificate management incorrectly.

This causes your site to be served without HTTPS, which is insecure and may scare visitors.

Use the --certificate-management=automatic flag to let Google handle SSL certificates for you.

Summary

Use 'gcloud app domain-mappings create' to connect your custom domain to your app.

Verify domain mappings with 'gcloud app domain-mappings list'.

Check DNS settings with 'nslookup' to ensure your domain points to Google Cloud.

Practice

1. What is the primary purpose of setting up a custom domain in Google Cloud Platform (GCP)?

easy

A. To use your own website address instead of a default GCP URL

B. To increase the storage capacity of your GCP project

C. To enable automatic backups for your cloud resources

D. To create virtual machines with custom names

Solution

1. Step 1: Understand what a custom domain is

   A custom domain lets you use your own website address instead of a generic cloud URL.

2. Step 2: Identify the purpose in GCP context

   In GCP, custom domains help users access services with familiar URLs, improving branding and trust.

3. Final Answer:

   To use your own website address instead of a default GCP URL -> Option A

4. Quick Check:

   Custom domain = personal website address [OK]

Hint: Custom domain means your own website address, not default URL [OK]

Common Mistakes:

• Confusing custom domain with storage or VM settings
• Thinking it changes backup or machine names
• Assuming it increases resource limits

2. Which DNS record type must you configure to point your custom domain to a Google App Engine service?

easy

A. MX record

B. TXT record

C. SRV record

D. CNAME record

Solution

1. Step 1: Identify DNS record types for domain pointing

   CNAME records map a domain or subdomain to another domain name, commonly used for pointing to cloud services.

2. Step 2: Match with Google App Engine requirements

   Google App Engine custom domains require CNAME records to link your domain to their service address.

3. Final Answer:

   CNAME record -> Option D

4. Quick Check:

   Point domain to service = CNAME record [OK]

Hint: Use CNAME to point domain to cloud service address [OK]

Common Mistakes:

• Using MX records which are for email routing
• Using TXT records meant for verification
• Confusing SRV records which are for service location

3. Given this snippet configuring a custom domain in GCP App Engine, what will happen if the DNS is not properly set?

gcloud app domain-mappings create example.com --certificate-management=automatic

medium

A. The command will fail with a syntax error

B. The domain will be mapped but users cannot access the app via example.com

C. The app will be accessible immediately without DNS changes

D. The SSL certificate will not be issued

Solution

1. Step 1: Understand domain mapping command effect

   The command creates a domain mapping and requests SSL certificate automatically.

2. Step 2: Consider DNS role in accessibility

   If DNS records do not point to GCP, users cannot reach the app via the custom domain despite mapping.

3. Final Answer:

   The domain will be mapped but users cannot access the app via example.com -> Option B

4. Quick Check:

   Mapping without DNS update = no access [OK]

Hint: Mapping alone doesn't work without DNS pointing [OK]

Common Mistakes:

• Assuming command fails without DNS
• Thinking app is accessible immediately
• Believing SSL won't issue without DNS

4. You tried to add a custom domain to your GCP App Engine app but received an error: "Domain ownership verification failed." What is the most likely cause?

medium

A. You did not add the required TXT record to your domain's DNS

B. You used an incorrect CNAME record type

C. Your App Engine app is not deployed

D. You forgot to enable billing on your GCP project

Solution

1. Step 1: Understand domain ownership verification process

   GCP requires you to prove you own the domain by adding a TXT record to DNS.

2. Step 2: Identify cause of verification failure

   If the TXT record is missing or incorrect, verification fails and domain cannot be added.

3. Final Answer:

   You did not add the required TXT record to your domain's DNS -> Option A

4. Quick Check:

   Missing TXT record = ownership verification fail [OK]

Hint: Verify domain by adding TXT record in DNS [OK]

Common Mistakes:

• Confusing CNAME with TXT for verification
• Assuming app deployment affects verification
• Thinking billing status causes verification error

5. You want to serve your website on both example.com and www.example.com using GCP App Engine with HTTPS. Which setup correctly achieves this with minimal manual DNS management?

hard

A. Map both domains; create TXT records for SSL; manually upload certificates

B. Map only example.com in App Engine; create A record for www pointing to example.com IP; manually manage SSL

C. Map both domains separately in App Engine and create CNAME for www pointing to ghs.googlehosted.com; use automatic SSL

D. Map www.example.com only; create CNAME for example.com pointing to www; disable SSL

Solution

1. Step 1: Understand domain mapping for root and www

   Both example.com and www.example.com need mapping to serve content on both URLs.

2. Step 2: Use recommended DNS and SSL setup

   Google recommends CNAME for www to ghs.googlehosted.com and automatic SSL management for ease and security.

3. Final Answer:

   Map both domains separately in App Engine and create CNAME for www pointing to ghs.googlehosted.com; use automatic SSL -> Option C

4. Quick Check:

   Separate mapping + CNAME + auto SSL = best practice [OK]

Hint: Map both domains and use CNAME for www with auto SSL [OK]

Common Mistakes:

• Using A record for www which is not recommended
• Mapping only one domain and missing the other
• Disabling SSL or managing certificates manually unnecessarily