Please note that the contents of this offline web site may be out of date. To access the most recent documentation visit the online version .
Note that links that point to online resources are green in color and will open in a new window.
We would love it if you could give us feedback about this material by filling this form (You have to be online to fill it)



BIND syntax differences

The Cloud DNS API differs somewhat from the BIND syntax.

@ symbol
You must replace instances of @ with the domain of the zone.
Unqualified names
Short names, like the @ symbol, must be replaced with the full domain name. For example, the CNAME record for www must be changed to www.example.com. in the requests to the Cloud DNS API.
Multiple rows for the same type of record
For example, say you have two MX resource records (type field) for example.com (name field) that each have a different priority value. With the Cloud DNS API, you will create both of these resource records as a single change. The name and type field form a unique key for the records in the Cloud DNS API.
$TTL default value
The BIND syntax allows you to define a default time-to-live ( TTL ) value that will be used if a resource record does not specify its own TTL value. In the Cloud DNS API, you must define a TTL value for each resource record set.

The migration documentation helps walk through how you can move from a BIND zone file to Cloud DNS using the command-line tool or with the help of a Python script .

Authentication required

You need to be signed in with Google+ to do that.

Signing you in...

Google Developers needs your permission to do that.