# Google Cloud DNS CNAME and A record setup (https://dodomain.io/docs/guides/dns-providers/googleclouddns)

How to add a CNAME, A or TXT record at Google Cloud DNS: the host for a subdomain and the root domain (leave it blank), and how to check it's live.

{/* GENERATED by apps/docs/scripts/generate-dns-provider-guides.mts from packages/core/src/guides.ts — do not edit. Change the guide in core, run `pnpm --filter @dodomain/docs generate:dns-provider-guides`, commit both. scripts/check-dns-provider-guides.sh fails the build on drift. */}

These are the steps DoDomain's hosted connect flow shows a customer whose domain is managed at Google Cloud DNS, in Google Cloud DNS's own vocabulary. A product using DoDomain never writes them: [the connect flow](https://dodomain.io/docs/connect-flow) detects the provider, shows these steps beside the exact records to create, and verifies each record against the zone's authoritative nameservers. They are published here for your own support articles, and for anyone who wants to see the steps before they start.

Related definitions: [CNAME record](https://dodomain.io/glossary/cname-record), [A record](https://dodomain.io/glossary/a-record), [apex domain](https://dodomain.io/glossary/apex-domain).

## Where the records live [#where-the-records-live]

Open [Google Cloud DNS's DNS management](https://console.cloud.google.com/net-services/dns/zones) and pick the domain.

## How to add a CNAME or A record in Google Cloud DNS [#how-to-add-a-cname-or-a-record-in-google-cloud-dns]

1. Google Cloud console → Cloud DNS zones → click the zone for your domain.
2. On the Zone details page, click Add standard.
3. Enter DNS name, pick the Resource record type and fill in the value as below.
4. Click Create, then come back and click Verify.

## What to put in the Google Cloud DNS host field [#what-to-put-in-the-google-cloud-dns-host-field]

Enter the subdomain only in DNS name (e.g. `www`); the zone's domain is appended. Leave it blank for the apex — `@` does not create an apex record. For a record on the domain itself, leave the host field blank.

Whatever the panel calls the field — Name, Host, Hostname — DoDomain's connect flow shows the value to paste into it already in this provider's format, and shows the fully-qualified name it will verify next to it.

## Worth knowing [#worth-knowing]

* Bought the domain through Google Domains and never set up Cloud DNS? Google Domains registrations moved to Squarespace, so the records live in Squarespace Domains' DNS panel instead.

## Common questions [#common-questions]

### Where do I add DNS records at Google Cloud DNS? [#where-do-i-add-dns-records-at-google-cloud-dns]

Open [Google Cloud DNS's DNS management](https://console.cloud.google.com/net-services/dns/zones) and pick the domain.

### What goes in the host field at Google Cloud DNS? [#what-goes-in-the-host-field-at-google-cloud-dns]

Enter the subdomain only in DNS name (e.g. `www`); the zone's domain is appended. Leave it blank for the apex — `@` does not create an apex record. For a record on the domain itself, leave the host field blank.

### How do I check that a record at Google Cloud DNS is live? [#how-do-i-check-that-a-record-at-google-cloud-dns-is-live]

Look the name up with the free [DNS lookup](https://dodomain.io/tools/dns-lookup), which shows the authoritative answer next to what public resolvers return. DoDomain verifies against the authoritative nameservers, so a record can be correct there while resolvers still serve the old answer until its TTL expires.

## Check the record is live [#check-the-record-is-live]

A saved record is not yet a live record. DoDomain verifies against the zone's **authoritative** nameservers, which answer as soon as the provider publishes the change; public resolvers can lag behind for as long as the old answer's TTL. The free [DNS lookup](https://dodomain.io/tools/dns-lookup) shows both answers side by side for any name, and the [provider detector](https://dodomain.io/tools/provider-detector) tells you which provider serves a domain and whether a one-click path exists for it.

## If you are the product asking for this record [#if-you-are-the-product-asking-for-this-record]

You do not have to send customers here. Mint a connect session and the hosted flow shows these steps to your Google Cloud DNS customers on its own, then verifies and keeps monitoring the records — see [the connect flow](https://dodomain.io/docs/connect-flow) and the framework guides for [Next.js](https://dodomain.io/docs/guides/custom-domains-multi-tenant-nextjs), [Rails](https://dodomain.io/docs/guides/custom-domains-multi-tenant-rails), [Laravel](https://dodomain.io/docs/guides/custom-domains-multi-tenant-laravel) and [Django](https://dodomain.io/docs/guides/custom-domains-multi-tenant-django). A customer who wants their bare domain rather than a subdomain is the [apex question](https://dodomain.io/docs/apex-domains), which no provider panel solves on its own.

*Vocabulary checked against Google Cloud DNS's own help page on 2026-10-22: [https://cloud.google.com/dns/docs/records](https://cloud.google.com/dns/docs/records).*