Azure DNS signs a public zone when you switch it on, with algorithm 13 and compact denial of existence. It is not a registrar: the DS record goes to wherever the domain is registered.
| What it is | DNS host |
| DNSSEC | Yes |
| Signing | Opt-in per public zone |
| Algorithm | ECDSAP256SHA256 (13), DS digest SHA-256 |
| DS record | No — add it at the registrar |
Is DNSSEC working for your domain?
Enter a domain: we read the DS record at its registry and the keys its nameservers publish, check that they match and the signatures are current, and ask a validating resolver.
Turning it on at Azure DNS
- DNS zones, the zone, DNSSEC, Enable DNSSEC — or az network dns dnssec-config create.
- Read the DS from the zone’s signing keys and add it at the registrar. The status moves from “Signed but not delegated” to “Signed and delegation established”.
Before moving the domain or its DNS
Unsigning: remove the DS at the registrar, wait for its TTL, and go on only once the portal shows “Signed but not delegated”.
Worth knowing
Azure rolls the zone-signing key itself; rolling the key-signing key needs Microsoft support, and a new DS.
It uses compact denial of existence (RFC 9824), not NSEC or NSEC3.
Domains bought through App Service Domain cannot use DNSSEC.
What changed
- 7 November 2024 — DNSSEC signing for Azure public DNS zones announced in preview; it is now documented as supported.
Whose nameservers a domain uses: Azure DNS’s.
Sources
Checked on 27 September 2026 against these official sources:
- Overview of DNSSEC — learn.microsoft.com
- How to sign your Azure Public DNS zone with DNSSEC — learn.microsoft.com
- How to unsign your Azure Public DNS zone — learn.microsoft.com
- Unlocking the future: Azure networking updates on security, reliability, and high availability — azure.microsoft.com