starMeet Us at   SaaStr AI 2025   SF Bay Area,US   |   13 - 15 May, 2025

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

Published
Categorized as Knowledge Base

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.

            June 5, 2025

            Why More Traffic Isn’t Solving Your Lead Problem (And What Will)

            In the digital age, it's tempting to equate increased website traffic with business growth. More visitors should mean more ...

            Read Image

            June 4, 2025

            Big Impact, Small Team: 10 Lead Gen Tips for Lean Marketing Teams

            In today’s hyper-competitive digital landscape, marketing success is often portrayed as a function of budget and headcount. But if ...

            Read Image

            June 3, 2025

            AI SDR vs AI Marketing Copilot: What High-Performing GTM Teams Are Choosing in 2025

            Sales used to be about hustle. Then came data. Now it’s about decisions—made in milliseconds by AI. With the ...

            Read Image

            Subscribe to learn about new product features, the latest in technology, solutions, and updates.

            Leave a comment