Zone DTOs

The sections and tables below provide detailed information about the contents of the DTOs used for Zone API calls. When a DTO field consists of the contents of another DTO, a cross reference link to the associated DTO is provided. When possible, return links to the “parent” DTO are provided, along with links to the API calls that use the DTO.

 

 

Bind Upload – TTL Behavior during Zone Creation

First Scenario

When creating a Zone via bind upload, any records with the same owner and type, but have different TTLs (in the bind file), will be created with the lowest TTL value amongst all the records of the same owner and type (in the bind file).

For example, the following three records for the owner “txtrecord” and the type TXT, along with rdata and TTLs in one bind file:

  1. txtrecorddata1 with TTL 30
  2. txtrecorddata2 with TTL 500
  3. txtrecorddata3 with TTL 400

In this scenario, all three of the above records would be created with the TTL value 300.

Second Scenario

Similarly to the previous example, if you have records with the same owner and type in a bind file, but only some of the TTLs are provided for the records in the rrset, then all of the records of the rrset will inherit the lowest TTL value (provided in the bind file).

  1. txtrecorddata1 with no TTL
  2. txtrecorddata2 with TTL 500
  3. txtrecorddata3 with TTL 400

All of the above records in the example will be given the TTL value of 400. If none of the provided records have TTL values, then the TTL value for each record will be given the default TTL value of 86400.

 

JSON Example: New Primary Zone via Transfer

{
        "properties": {
            "name": "copy-example.com.",
            "accountName": "example",
            "type": "PRIMARY"
        },
        "primaryCreateInfo": {
            "forceImport": true,
            "createType": "TRANSFER",
            "nameServer": {
                "ip": "1.2.3.4",
                "tsigKey": "key",
                "tsigKeyValue":"value"
            }
        }
}