No NS records found for ns3-35.azure-dns.org.
Try azure-dns.org instead?
id 58130, opcode QUERY, rcode NOERROR, flags QR RD RA ;QUESTION ns3-35.azure-dns.org. IN NS ;ANSWER ;AUTHORITY azure-dns.org. 1800 IN SOA ns1-01.azure-dns.com. azuredns-hostmaster.microsoft.com. 6 7200 900 2419200 3600 ;ADDITIONAL
whatsmydns.net NS Record Lookup tool lets you query DNS servers and get instant results.
Name Server or NS lookups are used to determine the NS records associated with a domain.
Looking for easier to understand results? Use the Global DNS Checker tool.
NS records, known as Nameserver records are used to store the nameservers for a domain. The nameservers identify which DNS servers are responsible for managing DNS records for the domain.
An example NS record may look like the following:
| Record | Type | Value | TTL |
|---|---|---|---|
| example.com | NS | ns1.nameserver.com | 3600 |
example.com represents the domain of the record.
NS is the record type.
ns1.nameserver.com is the value of the record. This is the address of the nameserver for this domain. NS records cannot point to CNAME records.
3600 is the TTL (time to live) of the record in seconds, this example represents 1 hour. This means that when a record has had updates made to it, then it will take 1 hour to update.
Domains are typically configured with multiple NS records, this is important because if the nameservers for a domain are not configured correctly then this will mean that the website, email, or other services for the domain will not work.
To configure primary and secondary or backup nameservers multiple NS records should be created for the domain.
| Record | Type | Value | TTL |
|---|---|---|---|
| example.com | NS | ns1.nameserver.com | 3600 |
| example.com | NS | ns2.nameserver.com | 3600 |
