The fully qualified domain name where the record can be located.
A Boolean flag indicating whether or not parts of the record are unable to be explicitly managed.
A description of how a record relates to a PATCH operation.
{@code REQUIRE} indicates a precondition that record data must already exist.
{@code PROHIBIT} indicates a precondition that record data must not already exist.
{@code ADD} indicates that record data must exist after successful application.
{@code REMOVE} indicates that record data must not exist after successful application.
Note: {@code ADD} and {@code REMOVE} operations can succeed even if they require no changes when applied, such as when the described records are already present or absent.
Note: {@code ADD} and {@code REMOVE} operations can describe changes for more than one record.
Example: {@code { "domain": "www.example.com\", "rtype": "AAAA", "ttl": 60 }} specifies a new TTL for every record in the www.example.com AAAA RRSet.
The record's data, as whitespace-delimited tokens in type-specific presentation format. All RDATA is normalized and the returned presentation of your RDATA may differ from its initial input. For more information about RDATA, see Supported DNS Resource Record Types
A unique identifier for the record within its zone.
The latest version of the record's zone in which its RRSet differs from the preceding version.
The type of DNS record, such as A or CNAME. For more information, see Resource Record (RR) TYPEs.
The Time To Live for the record, in seconds. Using a TTL lower than 30 seconds is not recommended. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
An extension of the existing record resource, describing either a precondition, an add, or a remove. Preconditions check all fields, including read-only data like {@code recordHash} and {@code rrsetVersion}.