What DNS does not support

The DNS features hosted zones do not have, one line each.

Last updated 18 November 2026View as Markdown
  • Proof of ownership. Nothing checks a TXT challenge or the delegation before a zone or an app's custom domain is claimed; the first organization to claim a name holds it, and the real owner contacts Deutsche Cloud support.
  • The platform's own domain, anything under it, or anything above it, as a hosted zone.
  • A CNAME at the apex. Use an ALIAS for an app, load balancer, bucket website or CDN distribution, or A and AAAA for an address.
  • Other record types: no PTR, HTTPS, SVCB, NAPTR, DS or others beyond those in Record sets.
  • ALIAS in zone files: an import cannot carry one in, and an export writes it as a comment.
  • Zone transfers (AXFR, IXFR), and secondary nameservers outside the platform.
  • DS records for delegated children. A name delegated with NS records is answered as unsigned, even in a signed zone.
  • DNSSEC algorithms other than 13, and NSEC3. Denial of existence is compact NSEC, which does not let anyone walk the zone.
  • Latency-based, geoproximity and multivalue answer routing. Weighted and geolocation routing are supported (see Route by weight or location).
  • Failover health checks on types other than A, AAAA and CNAME. In a weighted or geolocation set, the variants of MX, TXT and SRV sets can have health checks too. An ALIAS takes none and cannot be routed: it follows its target.
  • Routing in the console. The console shows routing variants, but creating or changing them takes the CLI, the API or Terraform.
  • Changing the name or type of a record set, or the domain of a zone.
Did this page help you?