gcloud dns record-sets export - export your record-sets into a file
gcloud dns record-sets export RECORDS_FILE --zone=ZONE, -z ZONE [--location=LOCATION] [--zone-file-format] [GCLOUD_WIDE_FLAG ...]
This command exports the record-sets contained within the specified managed-zone into a file. The formats you can export to are YAML records format (default) and BIND zone file format.
To export record-sets into a yaml file, run:
$ gcloud dns record-sets export records.yaml --zone=examplezonename
To export record-sets into a BIND zone formatted file instead, run:
$ gcloud dns record-sets export pathto.zonefile \ --zone=examplezonename --zone-file-format
Similarly, to import record-sets into a BIND zone formatted zone file, run:
$ gcloud dns record-sets import pathto.zonefile --zone-file-format \ --zone=examplezonename
- RECORDS_FILE
File to which record-sets should be exported.
- --zone=ZONE, -z ZONE
Name of the managed zone whose record sets you want to manage.
- --location=LOCATION
Specifies the desired service location the request is sent to. Defaults to Cloud DNS global service. Use --location=global if you want to target the global service.
- --zone-file-format
Indicates that records-file should be in the zone file format. When using this flag, expect the record-set to be exported to a BIND zone formatted file. If you omit this flag, the record-set is exported into a YAML formatted records file. Note, this format flag determines the format of the output recorded in the records-file; it is different from the global --format flag which affects console output alone.
These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, --help, --impersonate-service-account, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
These variants are also available:
$ gcloud alpha dns record-sets export
$ gcloud beta dns record-sets export