To request a domain’s DNS nameserver records on Windows, open Command Prompt and run nslookup -type=NS example.com., replacing the example with the exact domain you want to inspect. This is a read-only DNS query: it does not change your adapter’s DNS settings, move the domain to another provider or prove that a website is working.
The important distinction is between the DNS server answering your query and the nameservers named in the returned NS records. Those are different roles. Recording both prevents a common support mistake: assuming the server address printed at the top is necessarily the domain’s hosting provider.
Start with the domain, not the web address
Use a DNS name without an HTTPS prefix, path or browser query string. For example, a website address ending in a contact-page path is not a valid substitute for the domain itself. The trailing dot in the example marks an absolute DNS name and helps avoid search-suffix additions.
Choose the domain whose DNS administration you actually need to investigate. A website hostname such as www may not have its own NS records. Asking for NS records at that hostname is not equivalent to asking at the domain’s zone name. An empty answer for the hostname alone does not establish that the parent domain lacks nameservers.
On a workplace machine, stay on the approved network and use the organisation’s permitted resolver. DNS queries reveal the name being queried to the resolver; do not send internal names to an arbitrary public service.
Run a specific NS query
In Command Prompt, enter this command as one line:
nslookup -type=NS example.com.The example is a command pattern, not a prediction of the current nameserver list. Replace example.com with your intended public domain. Microsoft documents the noninteractive -type= option and defines NS as the DNS nameserver record type.
If support has supplied an approved DNS server, Microsoft’s command structure also allows that server as the second positional argument. Use the actual authorised address rather than copying an unrelated server from a forum. Selecting a resolver for one lookup does not change the Windows adapter configuration.
Read the header separately from the answer
First note the Server and Address header describing the server used for the query. Then inspect the answer section for the requested domain and its nameserver records. Do not treat an unrelated address printed alongside the response as an application connectivity result.
A non-authoritative answer can be a resolver’s answer rather than a direct response from an authoritative server. That label alone is not an error. Equally, a returned NS list is only DNS evidence from this query; it is not proof that every listed server is reachable, that a recent registrar change is complete, or that all users receive identical answers.
Keep a short record: exact domain, command, time, network used, answering server, returned NS names and any error text. After a DNS change, compare those records with the intended provider instructions. Do not repeatedly change the registrar configuration simply because one resolver still returns an unexpected result.
Separate missing records from failed queries
Microsoft distinguishes several failures. A timeout means the server did not respond within the request limits; it is not a negative record result. Refused means the server declined the request. Server failure also needs investigation rather than interpretation as an empty NS set.
Microsoft describes No records as a valid name without records of the selected query type, and Nonexistent domain as a name that does not exist. Before escalating either result, check spelling and whether you requested the correct domain rather than a web-page URL or unrelated subdomain.
If the network is unavailable, preserve the output and investigate that connection separately. Flushing caches, renewing DHCP leases or opening firewall ports is not part of this read-only record check. Our guide to comparing two DNS servers without changing Windows settings covers a separate follow-up task when using both servers is authorised.
Questions to answer before closing the ticket
Does an NS answer prove the website is online? No. It does not test HTTP, TLS, application health or successful sign-in.
Does this prove a provider migration is finished? No. Treat the result as one observation, not a complete delegation or propagation audit. Reconcile it with the provider’s expected configuration and independent checks appropriate to the change.
What should I send support? Send the exact query and relevant output, after reviewing it for private domain names or internal addresses. Say what you expected and which network produced the result; do not replace actual output with a guessed answer.
Sources: Microsoft’s nslookup modes, syntax and error definitions, and record-type definitions including NS. This is a documented workflow, not a claim that your Windows machine or DNS migration has been tested.
Educational use only. Test carefully before using steps in production. The site owner is not responsible for misuse, damage, data loss or production issues.
