You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow management of the SOA record using a friendly data structure and
avoid serial number conflicts if SOA-EDIT-API is used by reading the
latest serial number from the server before applying changes.
Signed-off-by: Georg Pfuetzenreuter <[email protected]>
*`zone` - (Required) The name of zone to contain this record.
40
+
*`name` - (Required) The name of the record, typically the same as `zone`.
41
+
*`type` - (Required) The record type, must be `SOA`.
42
+
*`ttl` - (Required) The TTL of the record.
43
+
*`mname` - (Required) SOA MNAME.
44
+
*`rname` - (Required) SOA RNAME.
45
+
*`serial` - (Required) SOA SERIAL - it will only be used for creation of the zone, subsequent changes are expected to use SOA-EDIT-API if a serial number update is desired. Set to `0` if no specific starting serial number is desired, or if the zone to manage already exists.
46
+
*`refresh` - (Required) SOA REFRESH.
47
+
*`retry` - (Required) SOA RETRY.
48
+
*`expire` - (Required) SOA EXPIRE.
49
+
*`minimum` - (Required) SOA MINIMUM.
50
+
51
+
### Attribute Reference
52
+
53
+
The id of the resource is a composite of the record name and record type, joined by a separator - `:::`.
54
+
55
+
For example, record `example.com.` of type `SOA` will be represented with the following `id`: `example.com.:::SOA`
0 commit comments