starWant to scale pipeline across web, email, ads and events? Grab the new GTM playbook Download Now

Guide to Adding TXT, MX, and CNAME Records in Google Cloud DNS (GCP)

Published
Categorized as Knowledge Base
Add MX Records in Google Cloud DNS
Add MX Records in Google Cloud DNS

Subscribe Now

    I allow Wyzard to send me regular updates and marketing communication as per its policy.

    Prerequisites

    • A Google Cloud account with a project.
    • A DNS zone created for your domain.

    Steps to Add Records

    Log in to Google Cloud Console:

    • Go to https://console.cloud.google.com/.

    Navigate to Cloud DNS:

    • From the left menu, select “Networking” > “Cloud DNS”.
    • Click on the DNS zone for your domain (e.g., example-com).

    Add Record Set:

    • Click “Add record set”.

    Adding a TXT Record

    • DNS Name: Enter the subdomain (e.g., sub.example.com.) or just example.com. for the root.
    • Resource Record Type: Select TXT.
    • TTL: Set to 3600 seconds (or customize).
    • TXT Data: Enter the text value in quotes (e.g., “v=spf1 include:_spf.google.com ~all”).

    Adding an MX Record

    • DNS Name: Enter example.com. for the root or a subdomain (e.g., mail.example.com.).
    • Resource Record Type: Select MX.
    • TTL: Set to 3600 seconds.
    • MX Data: Enter priority and server (e.g., 1 aspmx.l.google.com.), one per line. Include trailing dots.
    • Click “Create”.

    Adding a CNAME Record

    • DNS Name: Enter the subdomain (e.g., www.example.com.).
    • Resource Record Type: Select CNAME.
    • TTL: Set to 3600 seconds.
    • Canonical Name: Enter the target (e.g., example.com. or anotherdomain.com.).
    • Click “Create”.

    Save Changes:

    • Click “Create” for each record. Propagation may take a few minutes to hours.

    Reference

    Video: Create a Google Cloud DNS Zone from scratch in 8mins using Shared VPC
    Docs: https://cloud.google.com/dns/docs/records

    Notes

    • Propagation Time: DNS changes may take anywhere from a few minutes to 48 hours to propagate across the internet, depending on TTL settings and DNS provider.
    • Verification: Use tools like dig (e.g., dig example.com TXT) or nslookup to verify records after adding them.
    • Trailing Dots: AWS and GCP often require trailing dots for FQDNs (e.g., example.com.), while Azure and GoDaddy typically do not.

    This guide ensures you can configure DNS records efficiently. For specific use cases (e.g., email setup, domain verification), refer to the service provider’s documentation.


    Other blogs

    The latest industry news, interviews, technologies, and resources.

    July 18, 2025

    What Is Lead Qualification and How Does It Work? A Comprehensive Guide

    80% of sales teams waste time chasing leads that were never going to buy. Meanwhile, qualified prospects slip through ...

    Read Image

    Why INBOUND 2025 Matters for AI‑First GTM

    How a West‑coast debut, record attendance, and a surge of AI innovation set the stage for Wyzard.ai’s biggest ...

    Read Image

    July 2, 2025

    What Is Lead Scoring? Best Practices and How to Build a Scoring Model

    Imagine Sarah from Acme Corp just downloaded your pricing guide, attended yesterday's product demo, and clicked "Talk to Sales", ...

    Read Image

    Leave a comment