Whether or not the zone will be rectified on data changes via the API
Whether or not this zone is DNSSEC signed (inferred from presigned being true XOR presence of at least one cryptokey with active being true)
The SOA serial as seen in query responses. Calculated using the SOA-EDIT metadata, default-soa-edit and default-soa-edit-signed settings
Opaque zone id (string), assigned by the server, should not be interpreted by the application. Guaranteed to be safe for embedding in URLs.
Zone kind, one of "Native", "Master" and "Slave"
The id of the TSIG keys used for master operation in this zone
List of IP addresses configured as a master for this zone (“Slave” type zones only)
Name of the zone (e.g. "example.com."). MUST have a trailing dot
MAY be sent in client bodies during creation, and MUST NOT be sent by the server. Simple list of strings of nameserver names, including the trailing dot. Not required for slave zones.
The SOA serial notifications have been sent out for
Whether or not the zone uses NSEC3 narrow
The NSEC3PARAM record
Whether or not the zone is pre-signed
RRSets in this zone (for zones/{zone_id} endpoint only; omitted during GET on the .../zones list endpoint)
The SOA serial number
The id of the TSIG keys used for slave operation in this zone
The SOA-EDIT metadata item
The SOA-EDIT-API metadata item
Set to "Zone"
API endpoint for this zone
MAY contain a BIND-style zone file when creating a zone
Generated using TypeDoc
MAY be set. Its value is defined by local policy