Azure-docs: Name servers with dot in the end

[zoltanbedi]

So the name servers contains a dot in the end when I copied them from Azure. Is this correct/valid? Is this the way I should provide them in my registrars management page?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 4cb21b82-0660-2c3f-1651-86285fa64e59
• Version Independent ID: 2829303e-b6ba-537c-2751-8497e3d591cc
• Content: Delegate your domain to Azure DNS
• Content Source: articles/dns/dns-delegate-domain-azure-dns.md
• Service: dns
• GitHub Login: @KumudD
• Microsoft Alias: kumud

[AdamS-MSFT]

@B3zo0 Thank you for the valuable feedback,we are investigating the issue.

[subsarma]

Yes the trailing dot is correct and indicates the end of the fully qualified domain name (i.e the name server names are FQDNs). Some registrars may try to append the period if the NS name doesn't have it at the end, but to be compliant with DNS RFC we need to have the trailing period as we cannot assume every registrar will do this append.

[KumudD]

As per Subra's comment the trailing dot is accurate. Thanks!

please-close

[zoltanbedi]

thank you! 😊

[samueltuyizere]

can i copy the nameservers without the dot? my provider doesn't accept it with dots

[stofte]

@samueltuyizere If your API/UI doesn't accept the dot, yes, you can PROBABLY leave it out. It's more of a convention then anything. Eg most browsers should accept the address "https://www.google.com." (Note the trailing do, it still goes to the regular google.com ofc).