June 16, 2026 · 11 min read

Master nslookup Commands: A Comprehensive Guide

Unlock the power of nslookup commands! Learn how to diagnose DNS issues, test servers, and retrieve various record types with this essential guide.

June 16, 2026 · 11 min read

Networking DNS Command Line

Understanding your network and how it communicates is crucial, and at the heart of this understanding lies the Domain Name System (DNS). When you type a website address into your browser, it's DNS that translates that human-readable name into a machine-readable IP address. But what happens when this process falters? How do you troubleshoot these critical connections?

The nslookup command is your indispensable tool for this task. It's a powerful utility found on most operating systems, designed to query DNS servers and retrieve information about domain names, IP addresses, and other DNS records. Whether you're a seasoned network administrator, a web developer, or simply a curious tech enthusiast, mastering nslookup commands can significantly enhance your ability to diagnose and resolve network issues.

This guide will take you on a deep dive into the world of nslookup, exploring its fundamental uses, common commands, and practical applications. We'll cover how to use nslookup on both Linux and Windows, explain how to query specific DNS record types, and even touch on online tools for broader testing.

What is nslookup and Why Use It?

At its core, nslookup (which stands for "name server lookup") is a command-line utility that allows you to query the Domain Name System (DNS) to obtain domain name or IP address mapping, or for any other DNS record. Think of it as your personal DNS detective, asking questions of DNS servers to get the information you need.

The primary purpose of using nslookup is to diagnose DNS resolution problems. If a website isn't loading, or an email isn't being delivered, DNS issues are often the culprit. nslookup helps you determine if the DNS server is responding correctly, if the domain name is correctly mapped to an IP address, and if the correct DNS server is being queried.

Beyond basic troubleshooting, nslookup is invaluable for:

Verifying DNS records: Confirming that A records (for IP addresses), MX records (for mail servers), NS records (for name servers), TXT records (for verification and policy), and other DNS record types are configured correctly.
Testing DNS server connectivity: Ensuring that your specified DNS server is reachable and functioning.
Identifying DNS propagation: Observing how changes to DNS records are spreading across the internet.
Gathering network information: Obtaining details about a domain's DNS infrastructure.

It's a fundamental nslookup use case that empowers users to gain visibility into the often-invisible DNS layer of the internet.

Using nslookup on Windows and Linux

The nslookup utility is available on both major operating systems, though the interface and some nuances might differ slightly. The fundamental operation, however, remains the same.

nslookup on Windows

On Windows, you can access nslookup through the Command Prompt (cmd.exe) or PowerShell. Simply open your preferred command-line interface and type nslookup.

Basic Usage:

To check the IP address associated with a domain, type nslookup followed by the domain name:

C:\> nslookup google.com

This will query your system's default DNS server and return the IP address(es) for google.com. You'll typically see output like this:

Server:  your.dns.server.ip
Address:  your.dns.server.ip

Non-authoritative answer:
Name:    google.com
Addresses:  2607:f8b0:400a:809::2004
          172.217.160.142

Server: Shows the DNS server that responded to your query.
Address: The IP address of the DNS server.
Non-authoritative answer: Indicates that the DNS server queried is not the authoritative name server for the domain, but rather a caching server.
Name: The domain name you queried.
Addresses: The IP address(es) for the domain (IPv6 and/or IPv4).

To query a specific DNS server, you can use the following syntax:

C:\> nslookup google.com 8.8.8.8

This command tells nslookup to query Google's public DNS server (8.8.8.8) for information about google.com.

nslookup on Linux

On most Linux distributions, nslookup is also available by default. You'll use it in a terminal window.

Basic Usage:

Similar to Windows, you type nslookup followed by the domain name:

user@hostname:~$ nslookup google.com

The output will be very similar to the Windows version, showing the DNS server and the IP addresses for the queried domain.

Querying a Specific Server:

To query a specific DNS server on Linux:

user@hostname:~$ nslookup google.com 8.8.8.8

Interactive Mode:

Both Windows and Linux nslookup offer an interactive mode, which is incredibly useful for performing multiple queries without retyping the nslookup command each time. To enter interactive mode, simply type nslookup and press Enter:

C:\> nslookup
Default Server:  your.dns.server.ip
Address:  your.dns.server.ip

>

Or on Linux:

user@hostname:~$ nslookup
>

Once in interactive mode (indicated by the > prompt), you can type domain names, IP addresses, or specific commands. To exit, type exit.

This interactive mode is a key nslookup tool for efficient nslookup testing.

Advanced nslookup Commands and Their Uses

nslookup is far more than just a tool to find IP addresses. Its real power lies in its ability to query for specific DNS record types. This is where you can truly leverage the nslookup tool for in-depth network analysis.

Querying Specific Record Types (`nslookup type`)

By default, nslookup often returns 'A' records (IPv4 addresses). However, DNS stores various types of records, each serving a specific purpose. You can specify the record type you want to query using the set type= command within nslookup's interactive mode, or by appending it to your command in non-interactive mode.

Here are some of the most common and useful record types you can query:

A Record (nslookup a record): This is the most common type, mapping a hostname to an IPv4 address. This is usually the default.
```
# Linux/macOS
user@hostname:~$ nslookup -type=A google.com

# Windows
C:\> nslookup -type=A google.com
```
AAAA Record: Similar to 'A' records, but maps a hostname to an IPv6 address.
```
user@hostname:~$ nslookup -type=AAAA google.com
```
MX Record (nslookup ns record is a typo, this should be nslookup mx record): Mail Exchanger records specify which mail servers are responsible for accepting email messages on behalf of a domain. This is crucial for email deliverability. When you send an email to [email protected], your mail server queries the DNS for example.com's MX records to find out where to send the email.
```
user@hostname:~$ nslookup -type=MX google.com
```
The output will show a preference number (lower is higher preference) and the mail server hostname.
NS Record (nslookup ns record): Name Server records indicate which DNS servers are authoritative for a domain. These are the servers that hold the official DNS records for that domain. Knowing the nslookup ns record is vital for understanding who manages a domain's DNS.
```
user@hostname:~$ nslookup -type=NS google.com
```
This will list the authoritative name servers for the domain.
TXT Record (nslookup type txt, nslookup txt record): Text records are versatile and can contain arbitrary text. They are commonly used for:
- SPF (Sender Policy Framework): To help prevent email spoofing by specifying which mail servers are allowed to send email on behalf of a domain.
- DKIM (DomainKeys Identified Mail): For email authentication.
- DMARC (Domain-based Message Authentication, Reporting & Conformance): A policy for email authentication.
- Domain verification: Used by services like Google Search Console to verify domain ownership.
```
user@hostname:~$ nslookup -type=TXT google.com
```
CNAME Record: Canonical Name records create aliases for other domain names. If www.example.com is a CNAME for example.com, then querying www.example.com will resolve to the IP address of example.com.
```
user@hostname:~$ nslookup -type=CNAME www.example.com
```
SOA Record: Start of Authority records provide authoritative information about a DNS zone, including the primary name server, administrator's email address, domain serial number, and timers relating to refreshing the zone.
```
user@hostname:~$ nslookup -type=SOA google.com
```
ANY Record (nslookup all records): While the ANY query type (often represented as * or ANY in some tools) was intended to retrieve all available record types, it's often disabled or not fully supported by DNS servers for security and performance reasons. Modern DNS practices recommend querying for specific record types instead. However, if you want to attempt to retrieve as much information as possible, you can try:
```
user@hostname:~$ nslookup -type=ANY google.com
```
Be aware that this might not return all records, and might primarily show NS and SOA records if supported.

Setting Options in nslookup

Interactive mode allows you to set various options to customize nslookup's behavior.

server <ip_address>: Changes the default DNS server to query for subsequent lookups.
root: Changes the default server to a root name server.
timeout <seconds>: Sets the number of seconds to wait for a response before timing out.
retry <number>: Sets the number of times to retry a query if no response is received.
set all: Displays all current nslookup options.

Common Troubleshooting Scenarios with nslookup

Let's look at some practical nslookup use cases for real-world problems.

Scenario 1: Website Not Loading

Check your own DNS resolution:
```
nslookup website.com
```
If this fails or returns an incorrect IP, the problem might be with your local DNS settings or your ISP's DNS server.
Test with a public DNS server:
```
nslookup website.com 8.8.8.8
```
If this works, it strongly suggests an issue with your default DNS server.
Check for MX records (if it's an email issue):
```
nslookup -type=MX website.com
```
Ensure the correct mail servers are listed.

Scenario 2: Verifying Domain Ownership for a Service

Many services (like Google Workspace, Microsoft 365, or SSL certificate providers) require you to add a TXT record to your DNS to verify domain ownership.

Add the TXT record: Follow the service's instructions to add the specific TXT record to your domain's DNS zone file via your domain registrar or DNS hosting provider.
Verify with nslookup: After a short propagation period, use nslookup to check if the record is visible:
```
nslookup -type=TXT yourdomain.com
```
Look for the specific verification string provided by the service.

Scenario 3: Identifying Authoritative Name Servers

This is useful when you're trying to delegate DNS management or understand who controls a domain's DNS.

nslookup -type=NS example.com

This command will list the servers that are officially responsible for example.com's DNS records.

nslookup Test and Online Tools

While the built-in nslookup command is powerful, there are times when you might want to perform a more comprehensive nslookup test or a nslookup online tool.

Online DNS Checkers: Websites like MXToolbox, DNSChecker.org, and Google's own Dig tool (which is similar in function to nslookup but often preferred by Linux users for its output) offer web-based interfaces. These tools allow you to perform DNS lookups from various locations around the world simultaneously, helping you identify geographically specific DNS issues. They often provide nslookup a record, nslookup txt record, and nslookup ns record checks, along with many others.
Bulk nslookup: For users who need to check DNS records for a large number of domains, there are specialized tools and scripts, both online and offline, that can perform bulk nslookup operations. This is incredibly efficient for large-scale audits or monitoring.

These tools complement the command-line nslookup by offering broader testing capabilities and user-friendly interfaces for non-technical users.

Frequently Asked Questions (FAQ)

Q: What is the difference between nslookup and dig?

A: Both nslookup and dig are command-line tools for querying DNS servers. dig (Domain Information Groper) is generally considered more powerful and flexible, especially on Linux/macOS systems, offering more detailed output and options. nslookup is simpler and more universally available, particularly on Windows.

Q: Why is my nslookup command not returning any results?

A: This could be due to several reasons: your internet connection is down, the DNS server you are querying is unreachable or down, the domain name you are querying doesn't exist, or there's a firewall blocking your DNS queries.

Q: How do I find the authoritative name servers for a domain using nslookup?

A: Use the command nslookup -type=NS domainname.com. This will return a list of servers that are designated as authoritative for that specific domain's DNS records.

Q: Can nslookup check all DNS records for a domain?

A: While nslookup has an ANY type query, it is often not fully supported by DNS servers and may not return all record types. It's generally recommended to query for specific record types like A, MX, TXT, and NS individually for reliable results.

Q: How can I use nslookup to test mail server connectivity?

A: You can use nslookup -type=MX domainname.com to find the mail servers responsible for a domain. Once you have the server names, you can try to connect to them using telnet or other mail client tools to test connectivity further.

Conclusion

The nslookup command is an indispensable part of any network troubleshooting toolkit. By understanding its various options and how to query different DNS record types, you can effectively diagnose a wide range of network and DNS-related issues. Whether you're on Windows or Linux, mastering nslookup commands empowers you to gain deeper insights into your network's infrastructure and ensure smooth online operations.

From basic IP lookups to verifying complex email configurations with nslookup txt record and nslookup ns record checks, this versatile tool will become a go-to for anyone working with networks and the internet.