CMD Simulator
Networkingnslookup

Nslookup Command: Query DNS Records and Troubleshoot Name Resolution

Master nslookup to query DNS servers, lookup IP addresses from hostnames, troubleshoot DNS issues, and verify DNS record types (A, MX, NS, TXT).

Rojan Acharya·
Share

The nslookup command is a DNS (Domain Name System) diagnostic tool that queries DNS servers to retrieve domain name or IP address information. Use nslookup hostname to find IP addresses for domain names (forward lookup), nslookup IP-address for reverse DNS lookups to find hostnames from IPs, and nslookup -type=recordtype hostname to query specific DNS record types including MX (mail servers), NS (nameservers), TXT (text records), and more. Essential for troubleshooting DNS resolution failures, verifying DNS configuration changes, and diagnosing email delivery issues.

Whether you're investigating why websites won't resolve, verifying DNS propagation after domain changes, troubleshooting email server configuration, or checking nameserver assignments, nslookup provides direct access to DNS infrastructure. System administrators, network engineers, and DevOps professionals rely on nslookup for DNS diagnostics, domain validation, and nameserver verification.

This comprehensive guide covers nslookup syntax, both non-interactive and interactive modes, querying all DNS record types (A, AAAA, MX, NS, CNAME, TXT, SOA, PTR), practical examples for DNS troubleshooting, interpreting authoritative vs non-authoritative answers, and frequently asked questions. By the end, you'll confidently use nslookup to diagnose DNS issues and validate domain configurations.

What Is Nslookup?

Nslookup (Name Server Lookup) is a built-in command-line utility for querying DNS servers to obtain domain name or IP address mapping information. It's available in Windows, Linux, macOS, and virtually all operating systems. In Windows, nslookup runs in Command Prompt (CMD), PowerShell, and Windows Terminal on all Windows versions from Windows 2000 through Windows 11 and Windows Server editions.

Unlike ping which tests connectivity or ipconfig which shows local DNS configuration, nslookup actively queries DNS servers to retrieve DNS records. This makes it invaluable for: verifying DNS server responses, diagnosing resolution failures, checking DNS record correctness, testing different DNS servers, and confirming DNS propagation after changes.

Syntax

nslookup [-option] [hostname | -] [server]

Non-Interactive Mode

Query DNS once and exit:

nslookup hostname [dns-server]
nslookup -type=record-type hostname [dns-server]

Interactive Mode

Enter interactive mode for multiple queries:

nslookup
> hostname
> set type=record-type
> hostname
> exit

Parameters and Options

ParameterPurposeUse Case
hostnameDomain name or IP to queryRequired; what to look up
dns-serverDNS server IP to query (optional)Test specific DNS server
-type=AQuery A records (IPv4 addresses)Default; find IPv4 address
-type=AAAAQuery AAAA records (IPv6 addresses)Find IPv6 address
-type=MXQuery MX records (mail servers)Email troubleshooting
-type=NSQuery NS records (nameservers)Find authoritative nameservers
-type=CNAMEQuery CNAME records (aliases)Find canonical name
-type=TXTQuery TXT recordsSPF, DKIM, verification records
-type=SOAQuery SOA records (zone authority)Find primary nameserver, serial
-type=PTRQuery PTR records (reverse lookup)IP to hostname mapping
-type=ANYQuery all available recordsComprehensive record view
-debugEnable debug modeVerbose DNS query information
-timeout=secondsSet query timeoutAdjust for slow DNS servers

Parameters and Options Explained

Basic Forward Lookup (Hostname to IP)

Query DNS for IPv4 address (A record) of domain name. Most common nslookup usage.

Example:

nslookup google.com

Output:

Server:  dns.google
Address:  8.8.8.8

Non-authoritative answer:
Name:    google.com
Addresses:  142.250.185.46

Shows DNS server queried, and resolved IP address(es).

Basic Reverse Lookup (IP to Hostname)

Query DNS for hostname associated with IP address (PTR record).

Example:

nslookup 8.8.8.8

Output:

Server:  dns.google
Address:  8.8.8.8

Name:    dns.google
Address:  8.8.8.8

Returns hostname if PTR record exists.

Query Specific DNS Server

Direct query to specific DNS server instead of default configured server.

Example:

nslookup google.com 1.1.1.1

Queries Cloudflare's DNS (1.1.1.1) instead of your configured DNS server. Useful for testing different DNS servers or bypassing problematic local DNS.

Query MX Records (Mail Servers)

Retrieve mail exchange records to find mail servers for domain.

Example:

nslookup -type=MX google.com

Output:

google.com      MX preference = 10, mail exchanger = smtp.google.com

Shows mail server priority and hostname. Essential for email delivery troubleshooting.

Query NS Records (Nameservers)

Find authoritative nameservers for domain.

Example:

nslookup -type=NS google.com

Output:

google.com      nameserver = ns1.google.com
google.com      nameserver = ns2.google.com
google.com      nameserver = ns3.google.com
google.com      nameserver = ns4.google.com

Shows which DNS servers are authoritative for domain.

Query TXT Records

Retrieve text records used for SPF, DKIM, domain verification, and other purposes.

Example:

nslookup -type=TXT google.com

Output shows various TXT records:

google.com      text = "v=spf1 include:_spf.google.com ~all"
google.com      text = "google-site-verification=..."

Query CNAME Records (Aliases)

Find canonical name for alias domains.

Example:

nslookup -type=CNAME www.example.com

Shows if <www.example.com> is alias pointing to another hostname.

Query SOA Records (Start of Authority)

Retrieve zone authority information including primary nameserver, responsible person, and zone serial number.

Example:

nslookup -type=SOA google.com

Output shows:

  • Primary nameserver
  • Responsible party email
  • Serial number (zone version)
  • Refresh, retry, expire intervals
  • Minimum TTL

Interactive Mode

Enter interactive mode for multiple queries without retyping nslookup.

Example:

nslookup
> google.com
> set type=MX
> google.com
> set type=NS
> google.com
> exit

Efficient for multiple related queries.

Examples

This section covers practical nslookup usage for DNS diagnostics and troubleshooting.

Example 1: Find IP Address for Domain

Scenario: Need to know IP address for website or server.

Command:

nslookup google.com

Explanation: Returns IPv4 address(es) for domain. Multiple addresses indicate load balancing or CDN. Use IP for direct access or IP-based firewall rules.

Example 2: Verify DNS Resolution Works

Scenario: Website won't load; need to determine if DNS resolution is working.

Command:

nslookup problematic-site.com

Explanation: If returns IP address, DNS works—problem is elsewhere (network routing, firewall, server down). If fails with "can't find" error, DNS resolution is the issue.

Example 3: Test Different DNS Server

Scenario: Local DNS server might be misconfigured; want to test alternative DNS.

Commands:

nslookup example.com
nslookup example.com 8.8.8.8
nslookup example.com 1.1.1.1

Explanation: First uses default DNS server. Second tests Google DNS. Third tests Cloudflare DNS. Different results indicate local DNS server issues.

Example 4: Check Mail Server Configuration

Scenario: Email delivery failing; need to verify MX records are correct.

Command:

nslookup -type=MX example.com

Explanation: Shows mail servers for domain with priority values. Verify these match expected mail server hostnames. Lower priority number = higher priority for delivery.

Example 5: Find Authoritative Nameservers

Scenario: Need to know which nameservers control domain's DNS records for support ticket or DNS transfer.

Command:

nslookup -type=NS example.com

Explanation: Lists authoritative nameservers. Contact these servers' operators for DNS changes. Useful for verifying domain registrar configuration.

Example 6: Verify DNS Propagation After Changes

Scenario: Changed DNS records; want to verify changes have propagated.

Commands:

nslookup example.com 8.8.8.8
nslookup example.com 1.1.1.1
nslookup -type=NS example.com

Explanation: Query multiple public DNS servers to check if changes are visible. Query authoritative nameserver to verify changes are committed. DNS propagation can take minutes to hours.

Example 7: Reverse Lookup to Identify Host

Scenario: Have IP address from logs; want to identify hostname.

Command:

nslookup 142.250.185.46

Explanation: Performs reverse DNS lookup (PTR record query). Returns hostname if reverse DNS is configured. Useful for log analysis and identifying connection sources.

Example 8: Check SPF Record for Email Authentication

Scenario: Troubleshooting email authentication or spam issues; need to verify SPF record.

Command:

nslookup -type=TXT example.com

Explanation: TXT records include SPF (v=spf1...), DKIM keys, domain verification codes. SPF record specifies authorized mail servers for domain. Essential for email deliverability.

Example 9: Find IPv6 Address (AAAA Record)

Scenario: Need IPv6 address for dual-stack configuration or testing.

Command:

nslookup -type=AAAA google.com

Explanation: Returns IPv6 addresses (AAAA records) instead of IPv4 (A records). Useful for verifying IPv6 configuration or troubleshooting IPv6 connectivity.

Example 10: Interactive Mode for Multiple Queries

Scenario: Need to query multiple record types for same domain without retyping commands.

Commands:

nslookup
> server 8.8.8.8
> example.com
> set type=MX
> example.com
> set type=NS
> example.com
> set type=TXT
> example.com
> exit

Explanation: Interactive mode more efficient for multiple related queries. server command changes DNS server within interactive session. set type changes record type.

Common Use Cases

Nslookup serves diverse DNS troubleshooting and validation scenarios:

  • DNS Resolution Failure Diagnosis – When websites or services fail with "can't resolve hostname," use nslookup to verify DNS returns correct IP. If nslookup fails, problem is DNS (server misconfiguration, domain doesn't exist, DNS server unreachable). If succeeds, problem is application or network routing.

  • Verify DNS Server Functionality – Test if specific DNS server is responding correctly by querying it directly: nslookup domain 8.8.8.8. Compare results from different DNS servers to identify problematic ones. Critical when troubleshooting corporate DNS or ISP DNS issues.

  • DNS Propagation Verification – After changing DNS records (A, MX, NS), query multiple public DNS servers and authoritative nameservers to verify changes propagated. Different results from different servers indicate propagation in progress. Check every few hours until consistent.

  • Email Delivery Troubleshooting – Query MX records to verify mail server configuration: nslookup -type=MX domain.com. Incorrect or missing MX records cause email delivery failures. Verify priority values and mail server hostnames match email service provider requirements.

  • Domain Ownership Verification – Query TXT records to check domain verification codes for services like Google Workspace, Office 365, or website verification: nslookup -type=TXT domain.com. Essential during service setup or troubleshooting authentication.

  • Nameserver Identification – Find authoritative nameservers with nslookup -type=NS domain.com for: contacting DNS administrators, verifying domain registrar settings, diagnosing DNS delegation issues, or preparing domain transfers.

  • Reverse DNS Validation – Verify reverse DNS (PTR records) for email servers to prevent spam filtering. Query nslookup mail-server-IP should return matching hostname. Many spam filters reject mail from servers without proper reverse DNS.

  • CDN Configuration Verification – Check if domain points to CDN provider by querying A or CNAME records. Compare IPs to CDN provider's documented ranges. Verify CDN is properly configured before go-live.

  • DNS Cache Troubleshooting – When local DNS cache might be stale, query authoritative nameserver directly to get current records: nslookup domain authoritative-ns-IP. Compare to local DNS server results to identify caching issues.

  • Subdomain Enumeration – Query specific subdomains to verify they exist and resolve correctly: nslookup www.domain.com, nslookup mail.domain.com, nslookup ftp.domain.com. Part of infrastructure inventory and security auditing.

  • DNSSEC Validation – While nslookup has limited DNSSEC support, can verify if domain uses DNSSEC by querying DS or DNSKEY records (advanced usage). Important for security-critical domains.

  • Multi-Region DNS Testing – Query DNS servers in different geographic regions to verify geo-distributed DNS configuration returns appropriate answers. Critical for CDN and multi-region deployments with geographic routing.

Tips and Best Practices

Master these nslookup techniques for effective DNS diagnostics:

  • Always Test Against Multiple DNS Servers – Query your local DNS, ISP DNS, and public DNS (8.8.8.8, 1.1.1.1) to identify whether issue is DNS server-specific or universal. Different results indicate DNS server misconfiguration or cached stale data.

  • Understand Authoritative vs Non-Authoritative Answers – "Non-authoritative answer" means DNS server returned cached result, not directly from authoritative source. For definitive current records, query authoritative nameserver directly (find with -type=NS first).

  • Query Authoritative Nameserver Directly for Truth – First find nameservers: nslookup -type=NS domain.com. Then query one: nslookup domain.com ns1.domain-nameserver.com. This bypasses all caching and shows actual current records.

  • Use -type=ANY Carefully – While -type=ANY theoretically returns all records, many DNS servers no longer support it due to DDoS amplification concerns. Query specific record types instead for reliable results.

  • Check TTL Values in Interactive Mode – In interactive mode with set debug or set d2, see TTL (Time To Live) values showing how long records are cached. Low TTL indicates changes expected soon; high TTL means long caching.

  • Verify Reverse DNS for Email Servers – Email server IP should have matching PTR record: if IP is 1.2.3.4 for mail.example.com, nslookup 1.2.3.4 should return mail.example.com. Mismatch causes spam filtering issues.

  • Compare Results Over Time for Propagation – After DNS changes, save nslookup output: nslookup domain > dns-check-1.txt. Check again hours later: nslookup domain > dns-check-2.txt. Compare to track propagation progress.

  • Use Interactive Mode for Efficiency – When troubleshooting single domain with multiple record types, interactive mode avoids retyping. Enter once, query multiple types, exit. Saves time during comprehensive DNS audits.

  • Test Both IPv4 and IPv6 – Modern domains should have both A (IPv4) and AAAA (IPv6) records. Query both: nslookup domain (A) and nslookup -type=AAAA domain. IPv6-only networks require AAAA records.

  • Document DNS Server IP Addresses – When DNS issues occur, knowing good alternative DNS servers is critical. Keep list: 8.8.8.8/8.8.4.4 (Google), 1.1.1.1/1.0.0.1 (Cloudflare), your ISP's DNS. Test which works best for your location.

  • Recognize "Can't find" vs Timeout Errors – "Can't find: Non-existent domain" means DNS server says domain doesn't exist. Timeout means DNS server unreachable or not responding. Different causes require different solutions.

  • Check MX Priority Values – Lower MX priority number = higher priority. Primary mail server typically priority 10, backup 20. If email fails to primary, delivery attempts backup. Verify mail servers exist and are reachable.

Troubleshooting Common Issues

"Can't find [domain]: Non-existent domain"

Problem: Nslookup returns error saying domain doesn't exist.

Cause: Domain actually doesn't exist, typo in domain name, DNS server doesn't have record, or DNS propagation incomplete after recent registration/changes.

Solution:

  1. Verify domain spelling carefully (common typo)
  2. Check if domain is registered using WHOIS lookup
  3. Try different DNS server: nslookup domain 8.8.8.8
  4. If newly registered, wait for propagation (can take 24-48 hours)
  5. Verify domain expiration hasn't lapsed

Prevention: Double-check domain names; use reputable registrars; monitor domain expiration dates; allow time for DNS propagation.

Nslookup Times Out or Doesn't Respond

Problem: Nslookup hangs or returns timeout error.

Cause: DNS server unreachable, firewall blocking DNS (port 53), network connectivity issue, or DNS server down.

Solution:

  1. Verify network connectivity: ping 8.8.8.8
  2. Check if can reach DNS server: ping configured-dns-server
  3. Test alternative DNS server: nslookup domain 8.8.8.8
  4. Check firewall allows UDP port 53 outbound
  5. Verify DNS server setting in ipconfig /all

Prevention: Configure reliable DNS servers; ensure firewall permits DNS traffic; have backup DNS servers configured.

Different Results from Different DNS Servers

Problem: Querying different DNS servers returns different IP addresses for same domain.

Cause: DNS propagation in progress after recent changes, DNS servers have stale cache with different TTL expiry times, or geo-distributed DNS returns location-specific answers.

Solution:

  1. Query authoritative nameserver for definitive answer: find with nslookup -type=NS domain, then query that nameserver directly
  2. If propagation issue, wait for TTL to expire and caches to refresh
  3. If geo-distributed intentionally, results varying by location is normal (CDN, global load balancing)

Prevention: Allow sufficient time for DNS propagation (use low TTL before changes if planning changes); understand geo-distributed DNS returns different answers by design.

"Non-authoritative answer" Message

Problem: Results show "Non-authoritative answer" prefix.

Cause: DNS server returned cached result rather than querying authoritative source directly.

Solution:

  1. This is normal behavior and usually acceptable
  2. For guaranteed current records, query authoritative nameserver: nslookup -type=NS domain to find it, then nslookup domain that-nameserver
  3. Cached answers are typically current unless very recent changes made

Prevention: No prevention needed—caching is normal DNS operation. Query authoritative when absolute certainty required.

No MX Record Found for Domain

Problem: Query for MX records returns no results or error.

Cause: Domain has no mail servers configured, MX records misconfigured, or domain not intended to receive email.

Solution:

  1. Verify domain actually should have email: not all domains do
  2. Check if A record exists as fallback: some systems deliver to A record if no MX
  3. Contact domain administrator or email service provider
  4. Verify MX records configured in DNS management interface

Prevention: Properly configure MX records when setting up email; test after configuration; monitor MX record presence.

Reverse Lookup (PTR) Fails or Returns Wrong Hostname

Problem: Nslookup of IP address doesn't return hostname or returns incorrect hostname.

Cause: PTR record not configured, reverse DNS zone not delegated properly, or PTR record points to wrong hostname.

Solution:

  1. PTR records managed by IP owner (usually ISP or hosting provider)
  2. Contact IP provider to configure reverse DNS
  3. For dedicated servers, request PTR record through hosting control panel
  4. Verify forward (A) and reverse (PTR) match for email servers

Prevention: Configure PTR records for mail servers and public-facing servers; verify forward and reverse DNS match; contact IP provider for PTR delegation.

Related Commands

ipconfig /all – View Local DNS Configuration

Before troubleshooting with nslookup, verify local DNS configuration with ipconfig. Shows which DNS servers your system uses, helps identify if DNS server IPs are correct.

Example: ipconfig /all shows DNS servers 8.8.8.8 and 8.8.4.4; if misconfigured, nslookup uses wrong servers.

ipconfig /flushdns – Clear Local DNS Cache

If nslookup to authoritative nameserver shows updated records but local resolution returns old data, flush local cache. Forces fresh DNS queries.

Example: DNS changed but browser still goes to old IP; ipconfig /flushdns then nslookup domain shows new IP.

ping – Verify Resolved IP is Reachable

After nslookup returns IP address, use ping to verify that IP is actually reachable. DNS working doesn't guarantee network connectivity.

Example: nslookup server.com returns 203.0.113.45; ping 203.0.113.45 tests if server is reachable.

dig (Linux/Unix) – Advanced DNS Query Tool

On Linux/macOS, dig is more powerful than nslookup with cleaner output format and more options. Windows users can install BIND tools to get dig. Preferred by DNS professionals.

Example: Dig provides more detailed output with TTL values, query times, and better formatting than nslookup.

host (Linux/Unix) – Simple DNS Lookup

On Linux/macOS, host command provides simpler DNS lookup interface than nslookup. Windows doesn't include host by default but can be installed.

Example: host google.com returns A, AAAA, and MX records in simple format.

PowerShell Resolve-DnsName – Modern DNS Query

PowerShell's Resolve-DnsName cmdlet provides DNS query functionality with object-based output for scripting. More powerful than nslookup for automation.

Example: Resolve-DnsName google.com -Type MX returns MX records as PowerShell objects for scripting.

Frequently Asked Questions

What does nslookup command do?

Nslookup queries DNS servers to retrieve domain name or IP address information. It performs forward lookups (domain to IP), reverse lookups (IP to domain), and queries specific DNS record types (MX, NS, TXT, CNAME, etc.). Essential for troubleshooting DNS resolution issues and verifying DNS configuration.

How do I use nslookup to find IP address?

Type nslookup domain.com and press Enter. Output shows IP address(es) for the domain. For example: nslookup google.com returns IPv4 addresses. To query specific DNS server, add server IP: nslookup google.com 8.8.8.8.

What does "Non-authoritative answer" mean?

"Non-authoritative answer" means the DNS server returned a cached result rather than querying the authoritative nameserver directly. This is normal behavior. For definitive current records, query the authoritative nameserver directly (find with nslookup -type=NS domain.com first).

How do I check MX records with nslookup?

Use nslookup -type=MX domain.com to query mail exchange records. Output shows mail server hostnames and priority values. Lower priority number means higher priority for email delivery. Essential for troubleshooting email delivery issues.

How do I perform reverse DNS lookup?

Type nslookup IP-address to query PTR record for that IP. For example: nslookup 8.8.8.8 returns dns.google. Reverse lookups verify IP-to-hostname mapping, important for mail server configuration and log analysis.

How do I query a specific DNS server?

Add DNS server IP after domain: nslookup domain.com 8.8.8.8 queries Google DNS. Or in interactive mode: nslookup, then > server 8.8.8.8, then > domain.com. Useful for testing different DNS servers or bypassing local DNS issues.

What DNS record types can nslookup query?

Nslookup can query: A (IPv4), AAAA (IPv6), MX (mail servers), NS (nameservers), CNAME (aliases), TXT (text records for SPF/DKIM/verification), SOA (zone authority), PTR (reverse lookup), and more using -type=recordtype syntax.

How do I use nslookup in interactive mode?

Type nslookup without parameters to enter interactive mode. Then enter commands: > domain.com to query, > set type=MX to change record type, > server 8.8.8.8 to change DNS server. Type > exit to quit interactive mode.

Why does nslookup work but browser doesn't load page?

Successful nslookup means DNS resolution works, but browser requires more: network routing to IP must work, web server must be running, firewall must allow HTTP/HTTPS, and server must respond properly. Use ping resolved-IP and telnet resolved-IP 80 to continue diagnosis.

How do I find authoritative nameservers for domain?

Use nslookup -type=NS domain.com to query NS records showing authoritative nameservers. These servers are definitive source for domain's DNS records. Query them directly for guaranteed current records bypassing all caching.

What does "Request timed out" mean in nslookup?

Timeout means DNS server didn't respond within timeout period (default 2 seconds). Causes: DNS server unreachable, firewall blocking port 53, DNS server overloaded, or network connectivity issue. Try different DNS server: nslookup domain 8.8.8.8.

How do I check TXT records for SPF or DKIM?

Use nslookup -type=TXT domain.com to retrieve all TXT records including SPF (v=spf1...), DKIM keys, domain verification codes, and other text records. Essential for email authentication troubleshooting and domain ownership verification.

Quick Reference Card

CommandPurposeUse When
nslookup google.comFind IP for domainBasic DNS lookup
nslookup 8.8.8.8Reverse lookup (IP to hostname)Identify host from IP
nslookup domain 8.8.8.8Query specific DNS serverTest alternative DNS
nslookup -type=MX domain.comFind mail serversEmail troubleshooting
nslookup -type=NS domain.comFind nameserversIdentify authoritative servers
nslookup -type=TXT domain.comGet TXT recordsCheck SPF, DKIM, verification
nslookup -type=AAAA domain.comFind IPv6 addressIPv6 configuration
nslookup then > domainInteractive modeMultiple queries efficiently
nslookup -type=CNAME www.domain.comCheck CNAME aliasVerify alias configuration
nslookup -type=SOA domain.comGet zone authority infoFind primary NS, serial number

Try Nslookup Yourself

Ready to master DNS diagnostics? Practice these commands in our interactive Windows Command Simulator where you can safely experiment with nslookup and see realistic DNS query results.

Explore our complete Windows Commands reference for detailed syntax and options for nslookup and 200+ other commands. For related network diagnostics topics, check out our guides on ipconfig, ping, tracert, and netstat.

Summary

The nslookup command is an essential DNS diagnostic tool that provides direct access to DNS infrastructure for troubleshooting resolution failures, verifying configurations, and validating domain records. From basic lookups with nslookup domain.com to comprehensive diagnostics with record-type queries (-type=MX, -type=NS, -type=TXT), alternative DNS server testing, and interactive mode for efficient multi-query sessions, nslookup offers complete DNS diagnostic capabilities.

Key concepts covered include forward vs reverse lookups, interpreting authoritative vs non-authoritative answers, querying different DNS record types for various purposes (MX for email, NS for nameservers, TXT for verification and authentication), and testing multiple DNS servers to isolate caching or configuration issues. Mastery of these concepts enables systematic DNS troubleshooting and configuration validation.

Remember that DNS uses caching at multiple layers—local system cache, DNS resolver cache, recursive DNS server cache. When troubleshooting, query authoritative nameservers directly for definitive current records. Find authoritative servers with -type=NS query, then query them directly to bypass all caching. This ensures you're seeing actual configured records, not stale cached data.

Common troubleshooting workflows use nslookup after basic connectivity tests: if website won't load, first verify DNS resolves with nslookup. If nslookup fails, problem is DNS (server configuration, domain doesn't exist, DNS server unreachable). If nslookup succeeds, problem is elsewhere (routing, firewall, server availability). This rapid isolation dramatically narrows diagnostic scope.

Practice nslookup regularly with various record types and different DNS servers to build proficiency. Learn to recognize normal vs abnormal responses, understand DNS propagation timing, and develop systematic approaches to DNS diagnostics. Combined with ipconfig for local configuration, ping for connectivity testing, and tracert for routing analysis, nslookup completes your network diagnostic toolkit for comprehensive problem-solving capabilities.