Azure DNS keeps records in record sets — every record of one type at one name. Names are relative to the zone, @ is the apex, and alias record sets let the root point at an Azure resource where a CNAME is not allowed.
| Name field | Relative to the zone; @ for the apex |
| TTL | 1 to 2,147,483,647 seconds, per record set |
| Alias at the root | Alias record sets (A, AAAA, CNAME) |
| DNSSEC | Available — sign the zone, add DS at the registrar |
| Nameservers | Four per zone: ns1-NN.azure-dns.com, .net, .org, .info |
Where the DNS records are
In the Azure portal, open DNS zones, choose the zone, then Record sets → + Add. A record set is every record of one type at one name, so a second TXT value at the same name is added to the existing set rather than as a new one.
What to type in the name field
Names are relative to the zone: www in the zone example.com is www.example.com. Azure uses @ for the apex by convention; for records such as SRV you enter the relative name only (_sip._tcp).
| You were given a record for | Type in the name field |
|---|---|
| The domain itself — SPF, verification codes, MX | @ |
| DMARC | _dmarc |
| A DKIM key (selector s1, for example) | s1._domainkey |
| A subdomain such as www or mail | www |
Adding a record
- Open DNS zones and choose the zone.
- Open Record sets and select + Add (or open the existing set of that name and type).
- Enter the name as in the table above and choose the type.
- Set the TTL and paste the value.
- Select OK. Azure’s nameservers serve it within about a minute.
Check the record you just added
Enter the full name — _dmarc.yourdomain.com, s1._domainkey.yourdomain.com — and the type. If it answers, it is published; if it is not there yet, try again after a few minutes.
TXT records and long DKIM keys
Enter a TXT value as one string in the portal: Azure splits it into 255-character pieces for you. A TXT record set holds up to 4,096 characters across all its records.
Pointing the root domain at a service
A CNAME is not allowed at the apex, but an alias record set is: set “Alias record set” to Yes and choose an Azure resource (a public IP, Traffic Manager, Front Door, CDN) or another record set in the zone. Azure keeps the answer in step with the resource.
DNSSEC
Azure DNS can sign a public zone: open the zone, then DNSSEC, and tick Enable DNSSEC. The status reads “Signed but not delegated” until you copy the DS values (key tag, algorithm, digest type, digest) to your registrar; then it becomes “Signed and delegation established”. Domains bought as App Service Domains cannot use DNSSEC.
Common mistakes
- Adding a second record set of the same name and type instead of adding the value to the existing one.
- A CNAME at a name that already has other records — Azure does not allow it.
- Delegating to only some of the four nameservers Azure assigns; use all four, exactly as shown.
- Internationalised names must be entered in punycode.
Setting up email? The exact records for each service are in our email setup guides; to watch a change reach resolvers worldwide, use the propagation checker.
Questions
How fast are Azure DNS changes?
Azure says new and changed records appear on its nameservers within 60 seconds; resolvers that cached the old answer keep it until its TTL expires.
Sources
Checked against Azure DNS’s own documentation on 25 September 2026:
- DNS Zones and Records Overview — learn.microsoft.com
- Alias records overview — learn.microsoft.com
- How to sign your Azure Public DNS zone with DNSSEC — learn.microsoft.com
- FAQ — Azure DNS — learn.microsoft.com