Opens in a new tab

azure-dns.com: Azure DNS’s nameservers

Four nameservers under azure-dns.com, .net, .org and .info — ns1-37.azure-dns.com to ns4-37.azure-dns.info, for example — mean the domain’s DNS is in Microsoft Azure DNS. Each zone is given four from a pool when it is created, whatever the domain’s own ending.

WhoseAzure DNS — Cloud provider
Nameserversns1-<n>.azure-dns.com, ns2-<n>.net, ns3-<n>.org, ns4-<n>.info
How they are givenFour per zone, from a pool; kept when the zone moves between resource groups
DNSSECYes — signing with algorithm 13; the DS goes to the registrar

Does your domain use Azure DNS’s nameservers?

Enter a domain: we ask its registry which nameservers it hands out, ask each of them for the zone, and say whose they are — and whether any does not answer or disagrees.

The names

Four names, one under each of azure-dns.com, .net, .org and .info — Microsoft’s own example:

ns1-37.azure-dns.com
ns2-37.azure-dns.net
ns3-37.azure-dns.org
ns4-37.azure-dns.info

Where to see and change them

In the Azure portal: DNS zones, the zone, then Overview. Enter all four at the registrar.

Worth knowing

Nameservers under your own domain (vanity nameservers) are not supported.

Azure DNS does not sell domains; domains bought through App Service Domain do not support DNSSEC.

Common mistakes

  • Using fewer than all four names: Microsoft says to use all four whatever the domain’s ending, and its service level depends on it.
  • A trailing dot left off, or doubled where the registrar adds its own.

Also: Adding DNS records at Azure DNS; Turning on DNSSEC at Azure DNS.

Sources

Checked on 27 September 2026 against these official sources:

Know when your nameservers change

Add your domain and we check its delegation and records on a schedule, and email you when the nameservers change or stop answering — a hijack, an expiry or a move half made. Free for your first domain.

Create a free account