The OCID of the attached VCN.
The OCID of the owning compartment.
The OCID of the default view.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
Example: {@code {"Operations": {"CostCenter": "42"}}}
The display name of the resolver.
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags.
Example: {@code {"Department": "Finance"}}
The OCID of the resolver.
A Boolean flag indicating whether or not parts of the resource are unable to be explicitly managed.
The current state of the resource.
The canonical absolute URL of the resource.
The date and time the resource was created in "YYYY-MM-ddThh:mm:ssZ" format with a Z offset, as defined by RFC 3339.
*Example:** {@code 2016-07-22T17:23:59:60Z}
The date and time the resource was last updated in "YYYY-MM-ddThh:mm:ssZ" format with a Z offset, as defined by RFC 3339.
*Example:** {@code 2016-07-22T17:23:59:60Z}
An OCI DNS resolver. If the resolver has an attached VCN, the VCN will attempt to answer queries based on the attached views in priority order. If the query does not match any of the attached views, the query will be evaluated against the default view. If the default view does not match, the rules will be evaluated in priority order. If no rules match the query, answers come from Internet DNS. A resolver may have a maximum of 10 resolver endpoints.
*Warning:** Oracle recommends that you avoid using any confidential information when you supply string values using the API.