Meta tags:
description=Add, update, and delete DNS records such as A, AAAA, CNAME, and MX records.;

Headings (most frequently used words):

resource, record, gcloud, api, console, and, sets, add, set, update, delete, of, view, for, records, stay, organized, with, collections, save, categorize, content, based, on, your, preferences, before, you, begin, collection, in, transaction, zone, details, import, export, what, next, terraform, products, pricing, support, resources, engage, permissions, required, this, task,

Text of the page (most frequently used words):
the (270), #record (159), dns (131), #resource (110), zone (110), for (90), example (85), name (83), set (81), and (54), sets (52), cloud (47), this (47), you (42), com (40), with (38), that (38), ttl (35), gcloud (33), create (33), records (30), type (29), managed (29), use (28), managed_zone (28), add (24), google (22), must (21), delete (19), transaction (19), its (18), suffix (17), replace (16), can (16), rrset_type (16), rrset_name (16), details (15), your (15), following (15), page (14), overview (14), command (14), domain (14), have (14), zones (14), update (14), file (13), 100 (13), view (13), manage (12), test (12), project_id (12), click (12), console (12), 198 (12), rr_data (12), list (12), see (11), export (11), want (11), enter (11), api (10), rrdatas (10), import (10), these (10), are (9), get (9), affiliated (9), existing (9), resourcerecordsets (9), follow (9), policies (8), which (8), also (8), matches (8), incoming (8), queries (8), project (8), value (8), changes (8), configure (8), thumb (7), information (7), when (7), bind (7), format (7), method (7), steps (7), multiple (7), seconds (7), sign (6), data (6), 300 (6), 21600 (6), flag (6), trailing (6), apex (6), https (6), googleapis (6), projects (6), managedzones (6), arbitrary (6), associated (6), values (6), record_type (6), dnssec (6), code (5), resources (5), more (5), resourcerecordset (5), formatted (5), dot (5), smtp (5), cname (5), rrsets (5), start (5), rrdata3 (5), rrdata2 (5), rrdata1 (5), only (5), time (5), dns_name (5), português (4), español (4), about (4), support (4), down (4), sample (4), soa (4), gcp (4), private (4), googledomains (4), into (4), zone_name (4), automatically (4), resolver (4), caches (4), note (4), number (4), roles (4), permissions (4), tools (4), management (4), monitoring (4), application (4), terms (3), samples (3), all (3), other (3), content (3), solutions (3), using (3), next (3), routing (3), kind (3), yaml (3), specify (3), files (3), names (3), without (3), they (3), from (3), select (3), server (3), types (3), deleted (3), before (3), how (3), apply (3), partial (3), workspace (3), live (3), whose (3), execute (3), unit (3), collection (3), field (3), guides (3), networking (3), access (3), security (3), armor (3), cross (3), 한국어 (2), 日本語 (2), עברית (2), brasil (2), italiano (2), indonesia (2), français (2), américa (2), latina (2), deutsch (2), english (2), site (2), youtube (2), started (2), status (2), pricing (2), products (2), understand (2), need (2), last (2), updated (2), 2026 (2), utc (2), otherwise (2), licensed (2), under (2), license (2), send (2), feedback (2), troubleshooting (2), operations (2), monitor (2), commands (2), isn (2), standard (2), supported (2), exported (2), alias (2), 192 (2), host1 (2), hostmaster (2), 3600 (2), 259200 (2), omit (2), end (2), gmail (2), rfc (2), specified (2), match (2), default (2), does (2), not (2), servers (2), new (2), either (2), cannot (2), required (2), update_mask (2), patch (2), rrset (2), one (2), save (2), edit (2), modify (2), describe (2), present (2), response (2), additional (2), mail (2), provider (2), post (2), wildcard_dns_name (2), wildcard (2), google_dns_managed_zone (2), parent_zone (2), hashicorptest (2), description (2), task (2), iam (2), documentation (2), sdk (2), languages (2), frameworks (2), infrastructure (2), costs (2), usage (2), storage (2), observability (2), migration (2), industry (2), distributed (2), hybrid (2), multicloud (2), databases (2), analytics (2), pipelines (2), compute (2), hosting (2), development (2), logging (2), threat (2), advanced (2), migrate (2), health (2), checks (2), cluster (2), product (2), reference (2), technology (2), areas (2), close (2), subscribe, newsletter, our, third, decade, climate, action, join, cookies, privacy, tech, twitter, events, blog, engage, training, certification, architecture, center, getting, github, system, release, notes, community, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, except, noted, java, registered, trademark, oracle, affiliates, developers, apache, creative, commons, attribution, find, common, issues, might, encounter, check, propagation, what, supports, exporting, skipped, has, policy, empty, rrdata, examplezonename, exports, any, fully, qualified, some, implementations, providers, dots, follows, standards, interprets, relative, therefore, importing, results, identical, probably, undesired, both, ptr, caution, remove, denotes, like, refers, however, treated, literally, defining, full, replaces, assigned, host, parent, delegating, overwrite, verify, correct, origin, previous, provide, copy, out, checkbox, listed, public, authoritative, authority, located, root, creates, 1034, their, permanently, removed, recovered, prevent, losing, deletion, calling, directly, paths, conflicting, two, same, different, exception, them, case, exist, after, making, necessary, updates, displays, contains, procedure, assumes, already, created, within, parameter, exact, maximum, limit, outputs, json, first, parameters, shows, tab, deliver, email, simple, transfer, protocol, setup, process, described, deletions, additions, part, creating, specifies, group, applied, entire, succeeds, fails, ensuring, never, left, inconsistent, state, cli, google_dns_record_set, 86400, terraform, comma, separated, item, depending, selected, populate, remaining, fields, menu, minutes, numeric, amount, cached, positive, integer, leave, blank, asterisk, subdomain, added, begin, admin, fetch, representation, change, retrieve, perform, been, granted, describes, categorize, based, preferences, stay, organized, collections, home, error, messages, audit, dashboard, troubleshoot, cost, estimation, optimization, locations, threats, detector, detection, tags, custom, constraints, enabled, keys, activate, vpc, service, controls, control, special, configurations, scopes, hierarchies, resolution, order, chase, operate, maintain, rules, dns64, scoped, scope, work, gke, internationalized, binding, reverse, lookup, peering, forwarding, quickstart, tutorial, key, best, practices, general, discover, free, skip, main,

Text of the page (random words):
add a collection of resource record sets in a transaction you can add multiple resource record sets by creating a transaction that specifies the changes a transaction is a group of one or more dns record changes that must be applied as a unit the entire transaction either succeeds or fails ensuring your data is never left in an inconsistent state you can create a transaction only by using the gcloud cli or the cloud dns api to create a transaction follow these steps gcloud to start a transaction use the gcloud dns record sets transaction start command gcloud dns record sets transaction start zone managed_zone replace managed_zone with the name of the managed zone whose resource record sets you want to manage for example my zone name to add a resource record set as part of a transaction use the gcloud dns record sets transaction add command gcloud dns record sets transaction add rr_data name dns_name ttl ttl type record_type zone managed_zone replace the following rr_data an arbitrary value associated with the resource record set for example 198 51 100 5 you can also enter multiple values rrdata1 rrdata2 rrdata3 for example 198 51 100 5 10 2 3 4 dns_name the dns or domain name of the record set to add for example test example com ttl the time to live ttl for the record set in number of seconds for example 300 record_type the record type for example a managed_zone the name of the managed zone whose resource record sets you want to manage for example my zone name to execute the transaction use the gcloud dns record sets transaction execute command gcloud dns record sets transaction execute zone managed_zone to add a wildcard transaction use the gcloud dns record sets transaction add command gcloud dns record sets transaction add zone managed_zone name wildcard_dns_name type record_type ttl ttl replace the following managed_zone the name of the managed zone whose resource record sets you want to manage for example my zone name wildcard_dns_name the dns or domain name of the resource record set that you want to add for example example com note the trailing dot record_type the record type for example cname ttl the ttl for the record set in number of seconds for example 300 api to create a transaction with new resource record sets use the changes create method post https dns googleapis com dns v1 projects project_id managedzones managed_zone changes deletions additions name dns_name type record_type ttl ttl rrdatas rr_data replace the following project_id your project id managed_zone your managed zone name or id dns_name the dns or domain name of the record set for example test example com note the trailing dot record_type the record type ttl the time to live ttl for the record set in number of seconds for example 30 rr_data an arbitrary value associated with the resource record set for example 198 51 100 5 you can also enter multiple values rrdata1 rrdata2 rrdata3 for example 198 51 100 5 10 2 3 4 to deliver email to your domain you must add mx records to your zone if you use google workspace as your simple mail transfer protocol smtp provider see the set up google workspace mx records support page otherwise use the mx record details from your provider and follow the setup process described for google workspace view resource record sets for a zone to view resource record sets for a zone follow these steps console in the google cloud console go to the cloud dns page go to cloud dns on the zones tab click the zone for which you want to view the resource record sets the zone details page shows the details of all the resource record sets in that zone gcloud to view the dns records for your zone use the gcloud dns record sets list command gcloud dns record sets list zone zone_name replace zone_name with the name of a dns zone in your project the command outputs the json response for the resource record set for the first 100 records you can specify these additional parameters limit maximum number of record sets to list name only list resource record sets with this exact domain name type only list records of this type if present the name parameter must also be present api to view the dns records for your zone use the resourcerecordsets list method get https dns googleapis com dns v1 projects project_id managedzones managed_zone rrsets replace the following project_id the id of the project managed_zone the managed zone that this resource record set is affiliated with for example my zone name the name of this resource record set must have the dns name of the managed zone as its suffix view details of a resource record set this procedure assumes that you have already created a resource record set within the managed cloud dns zone to view the details of an existing resource record set follow these steps console in the google cloud console go to the cloud dns zones page go to cloud dns zones click the zone that contains the resource record set click the resource record set for which you want to view the details the resource record set details page displays the details of the resource record set gcloud to view the details of an existing resource record set use the gcloud dns record sets describe command gcloud dns record sets describe rrset_name type rrset_type zone managed_zone replace the following rrset_name the dns name that matches the incoming queries with this zone s dns name as its suffix for example test example com rrset_type the resource record type of this resource record set for example a managed_zone the managed zone that this resource record set is affiliated with for example my zone name the name of this resource record set must have the dns name of the managed zone as its suffix api to get the details of an existing resource record set use the resourcerecordsets get method get https dns googleapis com dns v1 projects project_id managedzones managed_zone rrsets rrset_name rrset_type replace the following project_id the id of the project managed_zone the managed zone that this resource record set is affiliated with for example my zone name the name of this resource record set must have the dns name of the managed zone as its suffix rrset_name the dns name that matches the incoming queries with this zone s dns name as its suffix for example test example com rrset_type the record type of this resource record set for example a update a resource record set to modify a record set follow these steps console to apply a partial update to an existing resource record set follow these steps in the google cloud console go to the cloud dns zones page go to cloud dns zones click the zone for which you want to update the resource record set on the zone details page next to the resource record set that you want to update click edit edit after making the necessary updates click save note you cannot enter conflicting data for example if two records have the same name they must be of different types the only exception is if one of them is a cname record in which case only the cname record can exist gcloud to apply a partial update to an existing resource record set use the gcloud dns record sets update command gcloud dns record sets update rrset_name rrdatas rr_data ttl ttl type rrset_type zone managed_zone replace the following rrset_name the dns name that matches the incoming queries with this zone s dns name as its suffix for example test example com rr_data an arbitrary value associated with the resource record set for example 198 51 100 5 you can also enter multiple values rrdata1 rrdata2 rrdata3 for example 198 51 100 5 10 2 3 4 ttl the ttl in seconds that the resolver caches this resource record set for example 30 rrset_type the resource record type of this resource record set for example a managed_zone the managed zone that this resource record set is affiliated with for example my zone name the name of this resource record set must have the dns name of the managed zone as its suffix api to apply a partial update to an existing resource record set use the resourcerecordsets patch method patch https dns googleapis com dns v1 projects project_id managedzones managed_zone rrsets rrset_name rrset_type ttl ttl rrdatas rr_data update_mask paths rrset ttl rrset rrdatas note the update_mask is required when calling the api directly without gcloud replace the following project_id the id of the project managed_zone the managed zone that this resource record set is affiliated with for example my zone name the name of this resource record set must have the dns name of the managed zone as its suffix rrset_name the dns name that matches the incoming queries with this zone s dns name as its suffix for example test example com rrset_type the resource record type of this resource record set for example a ttl the ttl in seconds that the resolver caches this resource record set for example 30 rr_data an arbitrary value associated with the resource record set for example 198 51 100 5 you can also enter multiple values rrdata1 rrdata2 rrdata3 for example 198 51 100 5 10 2 3 4 delete resource record sets when you delete resource record sets their dns records are permanently removed they cannot be recovered to prevent losing your dns records export the resource record sets before deletion for information about how to export resource record sets see import and export resource record sets cloud dns public zones are authoritative and the name server ns and start of authority soa record types are located at the zone apex which is the root of that domain cloud dns automatically creates ns and soa records at the zone apex these records can t be deleted by using the cloud dns api and are automatically deleted when the zone is deleted for more information see rfc 1034 to delete resource record sets follow these steps console in the google cloud console go to the cloud dns page go to cloud dns zones records for the zone are listed on the zone details page to delete resource record sets in a zone click the name of the zone next to the resource record sets that you want to delete select the checkbox click delete record sets gcloud to delete an existing resource record set use the gcloud dns record sets delete command gcloud dns record sets delete rrset_name type rrset_type zone managed_zone replace the following rrset_name the dns name that matches the incoming queries with this zone s dns name as its suffix for example test example com rrset_type the resource record type of this resource record set for example a managed_zone the managed zone that this resource record set is affiliated with for example my zone name the name of this resource record set must have the dns name of the managed zone as its suffix api to delete an existing resource record set use the resourcerecordsets delete method delete https dns googleapis com dns v1 projects project_id managedzones managed_zone rrsets rrset_name rrset_type replace the following project_id the id of the project managed_zone the managed zone that this resource record set is affiliated with for example my zone name the name of this resource record set must have the dns name of the managed zone as its suffix rrset_name the dns name that matches the incoming queries with this zone s dns name as its suffix for example test example com rrset_type the resource record type of this resource record set for example a import and export resource record sets to copy resource record sets into and out of a managed zone you can use import and export commands you can import from and export to either the bind zone file format or the yaml file format gcloud to import a resource record set use the dns record sets import command gcloud dns record sets import z zone_name if you want to specify the file format of the zone file use the previous command with the zone file format flag if you omit the flag you must provide a yaml format zone file replace zone_name with a new name for your zone when you use the gcloud dns record sets import command with the replace origin ns flag it replaces the ns records for the zone with the ns records specified in the zone file these records must match the name servers assigned by cloud dns to host the zone they must also match the ns records specified in the parent delegating zone by default cloud dns does not overwrite ns records if you use this flag you must verify that the ns records are correct when you import record sets as a bind zone formatted file remove the at sign that denotes the zone s apex in the bind zone formatted file for a dns name like example com the at sign refers to example com however in cloud dns the at sign is treated literally when defining record names to create a resource record set for the zone s apex in cloud dns use the full domain name for example example com caution some dns implementations and providers export bind zone formatted files without trailing dots on domain name data in cname mx ptr and other records in zone files cloud dns follows rfc standards and interprets all domain names without a trailing dot as relative to the dns name of the zone therefore importing the following mx records into a zone with the dns name example com results in identical and probably undesired records for both in smtp in mx 5 gmail smtp in l google com in smtp example com in mx 5 gmail smtp in l google com example com to import your zone files add a trailing dot to the end of any domain names that must be fully qualified to export a resource record set use the dns record sets export command to specify that the resource record sets are exported into a bind zone formatted file use the zone file format flag for example example com 21600 in ns ns gcp private googledomains com example com 21600 in soa ns gcp private googledomains com cloud dns hostmaster google com 1 21600 3600 259200 300 host1 example com 300 in a 192 0 2 91 if you omit the zone file format flag export exports the resource record set into a yaml formatted records file gcloud dns record sets export example zone z examplezonename for example kind dns resourcerecordset name example com rrdatas ns gcp private googledomains com ttl 21600 type ns kind dns resourcerecordset name example com rrdatas ns gcp private googledomains com cloud dns hostmaster google com 1 21600 3600 259200 300 ttl 21600 type soa kind dns resourcerecordset name host1 example com rrdatas 192 0 2 91 ttl 300 type a cloud dns supports the alias record type which isn t a standard dns record type and isn t supported in bind if you re exporting resource record sets to bind alias records are skipped if a zone has a routing policy it is exported as a record with empty resource record data rrdata what s next to get information about gcloud commands for resource record sets see gcloud dns record sets to check the status of gcloud or api operations see monitor dns propagation to find solutions for common issues that you might encounter when using cloud dns see troubleshooting to get an overview of cloud dns see cloud dns overview send feedback except as otherwise note...