Cloud DNS for domain management in GCP - Mini Project: Build & Apply

Cloud DNS for domain management

📖 Scenario: You are managing a website and want to use Google Cloud DNS to handle your domain's DNS records. This will help direct visitors to your website by translating your domain name into the correct IP address.

🎯 Goal: Create a Cloud DNS managed zone, add a DNS A record to point your domain to an IP address, and configure the TTL (time to live) for the record.

📋 What You'll Learn

Create a managed zone named example-zone with DNS name example.com.

Set the DNS zone description to Example domain zone.

Add an A record named www.example.com. pointing to IP 203.0.113.10.

Set the TTL for the A record to 300 seconds.

💡 Why This Matters

🌍 Real World

Managing DNS records is essential for directing internet traffic to your website or services. Cloud DNS helps automate and manage these records in the cloud.

💼 Career

Cloud engineers and DevOps professionals often configure DNS zones and records to ensure reliable domain name resolution for applications.

1

Create the managed zone dictionary

Create a dictionary called managed_zone with keys name, dns_name, and description. Set name to "example-zone", dns_name to "example.com.", and description to "Example domain zone".

GCP

# Your code here

Hint

Use a Python dictionary with the exact keys and values as specified.

2

Create the DNS A record configuration

Create a dictionary called a_record with keys name, type, ttl, and rrdatas. Set name to "www.example.com.", type to "A", ttl to 300, and rrdatas to a list containing the string "203.0.113.10".

GCP

managed_zone = {
    "name": "example-zone",
    "dns_name": "example.com.",
    "description": "Example domain zone"
}
# Your code here

Hint

Remember that rrdatas is a list of IP addresses as strings.

3

Combine managed zone and DNS record into a configuration

Create a dictionary called dns_config with keys managed_zone and records. Set managed_zone to the previously created managed_zone dictionary and records to a list containing the a_record dictionary.

GCP

managed_zone = {
    "name": "example-zone",
    "dns_name": "example.com.",
    "description": "Example domain zone"
}
a_record = {
    "name": "www.example.com.",
    "type": "A",
    "ttl": 300,
    "rrdatas": ["203.0.113.10"]
}
# Your code here

Hint

Use the existing variables to build the combined configuration dictionary.

4

Add the final Cloud DNS API request structure

Create a dictionary called cloud_dns_request with keys zone and changes. Set zone to the managed_zone dictionary. Set changes to a dictionary with key additions set to the list containing a_record.

GCP

managed_zone = {
    "name": "example-zone",
    "dns_name": "example.com.",
    "description": "Example domain zone"
}
a_record = {
    "name": "www.example.com.",
    "type": "A",
    "ttl": 300,
    "rrdatas": ["203.0.113.10"]
}
dns_config = {
    "managed_zone": managed_zone,
    "records": [a_record]
}
# Your code here

Hint

This structure matches the Cloud DNS API request format for adding records.

Practice

1. What is the main purpose of Cloud DNS in domain management?

easy

A. To manage user access permissions

B. To store website files and images

C. To create virtual machines

D. To connect your domain name to your website or service

Solution

1. Step 1: Understand what Cloud DNS does

   Cloud DNS translates domain names into IP addresses so browsers can find your website or service.

2. Step 2: Identify the correct purpose

   Connecting domain names to services is the core function of Cloud DNS, not storing files or managing users.

3. Final Answer:

   To connect your domain name to your website or service -> Option D

4. Quick Check:

   Cloud DNS connects domain to service = A [OK]

Hint: Cloud DNS links names to IPs, not files or users [OK]

Common Mistakes:

• Confusing DNS with storage services
• Thinking DNS manages virtual machines
• Mixing DNS with user permission controls

2. Which of the following is the correct way to create a managed zone using gcloud CLI?

easy

A. gcloud dns managed-zones create my-zone --dns-name example.com --description "My zone"

B. gcloud dns create-zone my-zone example.com

C. gcloud create dns-zone --name my-zone --domain example.com

D. gcloud dns zones add my-zone example.com

Solution

1. Step 1: Recall the gcloud command syntax for creating managed zones

   The correct command uses 'gcloud dns managed-zones create' followed by the zone name and flags for DNS name and description.

2. Step 2: Match the correct syntax

   gcloud dns managed-zones create my-zone --dns-name example.com --description "My zone" matches the official syntax exactly, others use incorrect commands or flags.

3. Final Answer:

   gcloud dns managed-zones create my-zone --dns-name example.com --description "My zone" -> Option A

4. Quick Check:

   Correct gcloud create syntax = A [OK]

Hint: Use 'gcloud dns managed-zones create' with flags [OK]

Common Mistakes:

• Using wrong command verbs like 'create-zone'
• Omitting required flags like --dns-name
• Mixing command order or parameters

3. Given this DNS record in a managed zone:
example.com. IN A 192.0.2.1
What happens when a user types example.com in their browser?

medium

A. The browser connects to the IP address 192.0.2.1

B. The browser shows an error because A records are invalid

C. The browser redirects to example.com.com

D. The browser connects to a random IP address

Solution

1. Step 1: Understand the A record function

   An A record maps a domain name to an IPv4 address, here 192.0.2.1.

2. Step 2: Predict browser behavior

   When typing example.com, the browser looks up the A record and connects to the specified IP address.

3. Final Answer:

   The browser connects to the IP address 192.0.2.1 -> Option A

4. Quick Check:

   A record maps domain to IP = B [OK]

Hint: A record points domain to IP address [OK]

Common Mistakes:

• Thinking A records cause errors
• Confusing A record with redirects
• Assuming random IP connections

4. You tried to add a CNAME record for your domain root (example.com) but it failed. What is the likely reason?

medium

A. The TTL value was too high

B. You must use an MX record instead

C. CNAME records are not allowed at the root domain

D. You need to delete all A records first

Solution

1. Step 1: Recall DNS rules for CNAME records

   CNAME records cannot be set at the root domain because it conflicts with other essential records like NS and SOA.

2. Step 2: Identify the cause of failure

   Trying to add a CNAME at the root domain violates DNS standards, causing the failure.

3. Final Answer:

   CNAME records are not allowed at the root domain -> Option C

4. Quick Check:

   CNAME not allowed at root domain = C [OK]

Hint: Root domain cannot have CNAME records [OK]

Common Mistakes:

• Confusing CNAME with MX record usage
• Blaming TTL values for record rejection
• Thinking A records must be deleted first

5. You want to set up email for your domain example.com using Cloud DNS. Which DNS record type should you add to direct emails to your mail server?

hard

A. TXT record with your mail server IP

B. MX record pointing to your mail server domain

C. CNAME record pointing to your mail server domain

D. A record pointing to your mail server IP

Solution

1. Step 1: Identify the DNS record for email routing

   MX records specify mail servers responsible for receiving email for the domain.

2. Step 2: Understand why other records are incorrect

   A records map domain to IP but don't direct email; CNAMEs alias names but don't specify mail routing; TXT records hold text data, not mail routing.

3. Final Answer:

   MX record pointing to your mail server domain -> Option B

4. Quick Check:

   Email routing uses MX records = D [OK]

Hint: Use MX records to route email to mail servers [OK]

Common Mistakes:

• Using A or CNAME records for email routing
• Confusing TXT records with mail routing
• Not specifying mail server domain in MX record