Security in DNS
Who may do what with hosted zones (IAM), what is recorded in the audit log, and who may claim a domain.
IAM actions
Every request, through the API, the CLI, Terraform or the console, is checked against your IAM
policies. A zone's resource name has no region: rn:ews::<organization id>:dns:zone/<zone id>.
Every record action is checked against the zone, so a policy cannot grant one record set of a zone
without the others. Listing and creating zones are checked against rn:ews::<organization id>:dns:*.
| Action | Access | What it allows |
|---|---|---|
dns:ListZones | Read | List hosted zones and the platform nameservers |
dns:GetZone | Read | Describe a hosted zone and its delegation state |
dns:CreateZone | Write | Create a hosted zone for a domain |
dns:DeleteZone | Write · destructive | Delete a hosted zone and every record in it |
dns:CheckDelegation | Read | Look up whether the domain is delegated to the platform nameservers |
dns:ListRecords | Read | List the records of a hosted zone |
dns:ChangeRecords | Write · destructive | Create, update or delete records in a hosted zone |
dns:ImportZone | Write · destructive | Import records from a zone file |
dns:UpdateQueryLogging | Write | Turn query logging on or off for a hosted zone |
dns:GetQueryLog | Read | Read a hosted zone's query log (client networks, not addresses) |
dns:GetDnssec | Read | Describe a zone's DNSSEC state: its keys, the DS records for the registrar and what the parent serves |
dns:EnableDnssec | Write | Sign a hosted zone with DNSSEC |
dns:DisableDnssec | Write · destructive | Stop signing a zone once the parent no longer serves its DS (or at once) |
dns:RotateDnssecKey | Write | Start a rollover of a zone's key-signing or zone-signing key |
dns:CompleteDnssecKeyRollover | Write · destructive | Finish a key-signing key rollover now, removing the old key |
Generated from the service’s IAM descriptor. Sensitive reads hand over secret material or source code and are recorded in the audit log like writes; destructive writes delete, overwrite or revoke.
dns:ChangeRecordscovers adding, editing and deleting record sets;dns:ImportZoneis separate.- Exporting a zone file needs
dns:ListRecords. - Checking the DNSSEC chain of trust needs
dns:GetDnssec. - A key or an instance role that gets certificates through DNS-01 (see
Get wildcard certificates with Caddy) needs
dns:ListZonesonrn:ews::<organization id>:dns:*, anddns:ListRecordsanddns:ChangeRecordson the zone.
A policy for someone who may change the records of one zone only (replace org-id and zone-id):
{
"Version": "2024-01-01",
"Statement": [
{
"Effect": "Allow",
"Action": ["dns:GetZone", "dns:ListRecords", "dns:ChangeRecords"],
"Resource": "rn:ews::org-id:dns:zone/zone-id"
},
{
"Effect": "Allow",
"Action": ["dns:ListZones"],
"Resource": "rn:ews::org-id:dns:*"
}
]
}The zone's Access tab in the console shows who may act on the zone and, with
iam:AttachUserPolicy, grants access to it.
Audit
Creating and deleting zones, adding, editing, deleting and importing records, turning query logging on or off, and every DNSSEC change are recorded in the audit log, allowed or denied, once the request has passed its validation: a request with a malformed body, or an id that is not a UUID, is refused before the permission check and not recorded. Reads, including the delegation and DNSSEC checks, are recorded only when they are denied, at most once a minute per user and action.
Who may claim a domain
A hosted zone is answered on the internet as soon as the domain delegates to the platform nameservers, and nothing checks that you own the domain before you create its zone. So each domain is held by one organization:
| You claim | Refused when |
|---|---|
| A hosted zone | It is the platform's own domain, under it, or above it (400) |
| A hosted zone | Another organization holds the name, a name above it or a name below it, as a zone or an app's custom domain (409) |
| A hosted zone | It is inside one of your own zones (409); delegate it from that zone with an NS set instead |
| An app's custom domain | Another organization holds a zone that contains it, or the same domain on their app (409) |
The refusals for a hosted zone read " is the platform's own domain, so a zone cannot be it, sit under it, or enclose it", " is already a hosted zone on this platform, held by another organization" (or "a custom domain"), " overlaps , a hosted zone held by another organization" (or "a custom domain"), and " is inside , your zone".
A zone holds its whole tree, so example.com and shop.example.com cannot belong to two
organizations. A name is available to whoever claims it first: if someone else holds your domain,
contact Deutsche Cloud support.
Network exposure
The nameservers answer anyone on the internet over UDP and TCP port 53, for hosted zones only; they never look up other names. See How the nameservers answer.