DNS Commands for Windows: Diagnose, Test, and Fix DNS Issues

Imagine typing a website address into your browser, expecting the page to load instantly, only to encounter the message, “This site can’t be reached.” In many cases, the website itself is functioning perfectly—the real reason for this is the DNS.

Let’s decode this.

The Domain Name System (DNS) is similar to an Internet phone book. It provides the user with an easy-to-remember domain name, which is converted into an IP address that computers use to communicate with one another. When DNS is not operating properly, website pages load incorrectly, e-mail doesn’t reach the recipient, and servers fail to create connections to one another on a network.

Fortunately, Windows provides many built-in command-line tools that help diagnose and repair DNS-related issues in minutes. Although the GUI allows basic configuration, Command Prompt and PowerShell provide more detailed information.

In this detailed blog, we will walk through the most commonly used DNS commands for Windows, including DNS configuration settings, testing domain name resolution, viewing and clearing your DNS cache, verifying DNS records, and troubleshooting common connectivity and troubleshooting the common connectivity issues.

Regardless of whether you own a website, are a system administrator, or are a developer, these commands will assist you in diagnosing your DNS problems so that you can keep your Internet-based services running effectively.

What are Windows DNS commands?

Windows DNS commands are command-line utilities that allow the user to examine, test, repair, and troubleshoot their DNS configuration. These commands can be used directly rather than surfing multiple pages or tabs to quickly diagnose DNS issues.

Windows includes two main command-line environments for DNS troubleshooting: Command Prompt (CMD) and PowerShell.

Whether you’re troubleshooting a computer, website, or server, Windows DNS command-line tools help diagnose and resolve DNS issues quickly and efficiently.

Why is CMD run as administrator for DNS commands?

Some DNS commands require the user to have elevated permissions to alter the network configuration, delete the DNS cache, or reset components. To prevent any permission errors, it is strongly recommended that you open a Command Prompt with Administrator privileges before attempting to resolve any DNS issues.

Method 1: Launch CMD from the Start menu

1. Click the Start button (or press the Windows key)
2. Type “cmd” or “command prompt” in the search box
3. Right-click on the command prompt and choose “run as administrator”
4. Click “yes” when the User Account Control (UAC) prompt displays.

Method 2: Start CMD with the Run dialogue

1. Press Windows + R to open the Run dialogue box.
2. Type “cmd”
3. Rather than pressing ‘enter’, hold down the CTRL and SHIFT keys together, then press ‘enter’
4. Approve the User Account Control (UAC) message to start CMD as an administrator.

Method 3: Start CMD with Windows Terminal

1. Right-click the Start button (or press Windows + X).
2. Select “windows terminal (Admin)”
3. Click “yes” when prompted.
4. If the Windows terminal opens with PowerShell as the default type, open a CMD tab.

Once you have CMD opened with administrator access, you can perform DNS troubleshooting and repair without encountering any access issues.

What is the DNS troubleshooting workflow for Windows?

In situations where websites, email services, or domain resolution stop functioning correctly, users frequently change DNS settings without first diagnosing the root cause of the problem. Instead of that, a better way to work through these potential problems is to implement a structured process of identifying and then troubleshooting.

By following the process below in order, you’ll be able to determine where your DNS problem lies and apply the appropriate solution without any guesswork.

Using this process means that you’ll be able to diagnose DNS problems based on a methodical approach. The commands outlined in the following sections align each step within the troubleshooting workflow, thus making it simpler for you to identify and resolve Windows DNS-related issues.

Which are the essential DNS commands for Windows?

1. ipconfig /all

When troubleshooting Windows DNS-related issues, the first thing you need to do is run the ipconfig /all command. This gives you a comprehensive summary of your computer’s existing network configuration, including your computer’s current DNS servers for resolving domain names.

By reviewing this data, you’ll be able to quickly determine if your computer is connected to the right network and whether it is obtaining valid DNS settings through either DHCP or static configuration.

This DNS command filters the results and displays only DNS-related entries, making it easier to identify the DNS servers currently assigned to your system.

2. nslookup

One of the best utilities for troubleshooting DNS and verifying domain names is nslookup. It’s used to find out if a domain name is resolving correctly by sending a DNS query to the configured DNS server and returning the response to you. In simple language, it verifies whether the domain is resolving to the correct IP address.

Because nslookup communicates with DNS servers directly, it is the primary tool for diagnosing domain resolution issues, testing/confirming DNS changes, and determining whether the propagation status of DNS records is successful.

You can also use nslookup to check on public domains or to check on one or more DNS records of your website. If the returned IP address from nslookup does not match the IP address assigned to your website’s hosting server, either the DNS records are still being propagated, or there is a problem with how the DNS records were configured.

3. nslookup with a Specific DNS Server

In some cases, the issue is with the DNS server resolving the domain, not the domain itself. Thus, the standard nslookup command will only show you what’s happening on the specific DNS server. In order to get the real issue diagnosed, it must be checked against other DNS servers.

If you want to check whether different DNS providers can resolve a specific domain, you should test it using public DNS servers. This helps confirm whether the issue is only with your local DNS server.

When troubleshooting DNS issues, test the domain at least two different times on multiple locations using different public DNS servers.

4. ipconfig /displaydns

Whenever you access a website, Windows saves local results from DNS lookups in a temporary cache. This way, the next time you visit a website, you can connect faster (skipping the permission required for the DNS server for the same IP address). You can review the DNS cache to see how Windows is resolving domain names by using the command ipconfig /displaydns.

This command is particularly useful when troubleshooting DNS-related issues caused by outdated or incorrectly cached entries.

The ipconfig /displaydns command filters the normal output list of DNS caches. Therefore, only results for a specified domain are displayed. This functionality makes troubleshooting much easier.

5. ipconfig /flushdns

If any of the DNS cache entries stored in memory are outdated or incorrect, your computer continues to connect to the wrong server (even after updated DNS records). The command ipconfig /flushdns removes all DNS cache records from the local system, and hence, the next time you attempt to connect to a website, Windows obtains new DNS records from the configured DNS servers.

Because of this, ipconfig /flushdns is one of the most frequently used commands for troubleshooting DNS and is one of the first recommended fixes when a website does not load correctly after making DNS changes.

Clearing the DNS cache is one of the fastest methods to resolve access problems after DNS changes. However, if the website continues to resolve to an incorrect IP address even after the DNS cache has been cleared, it suggests that the changes are still propagating or the records themselves are incorrectly configured.

6. ipconfig /registerdns

The command to flush DNS cache clears stored DNS entries on your system; ipconfig /registerdns does the opposite and asks Microsoft to update and record your system’s DNS entries at the configured DNS server. By running this command, you are assuring that the DNS database contains the most up-to-date information for the DNS name associated with the server’s IP address.

This command is most helpful with devices in business networks, Windows Server environments, and Active Directory, where devices regularly register with the DNS server because of dynamic DNS registration.

If you run this command and your DNS entry does not immediately show an updated record, wait a few minutes for the DNS server to process the registration request. You can also check for errors in the Windows Event Viewer.

7. Ping Domain Name

While ping is commonly known as a tool for testing network connections, it is also useful for troubleshooting DNS issues. When Windows tries to send packets to a node on the Internet, it has to first resolve the respective node’s domain name to its corresponding IP address. Thus, this command verifies if DNS resolution is working properly.

Additionally, unlike nslookup, which only provides a way of resolving DNS queries, ping provides information on whether the destination (the IP address returned with DNS resolution) is reachable on the network.

To keep their network safe, many websites or servers purposely deny pinging (ICMP) requests. Thus, ping is used to test connectivity. If DNS resolves successfully but ping requests time out, the server may still be working, but it can appear as if there is no connection.

8. tracert Domain Name

To perform a more complete test run, use ‘nslookup’ and then run ‘tracert’. This determines the type of connection issue. When you receive an “A” record for your domain but your website/server has no connectivity from your computer, there may be routing problems between the paths (from your computer to the destination). Within the same line, run ‘tracert’ to exactly pinpoint where the network broke.

As mentioned above, tracert shows the router paths that data packets travel to get to the next router. With the tracert command, it is now possible to pinpoint where communication issues occurred due to routing errors or delays at points along the path the data travelled.

Always run tracert after getting a successful DNS resolution. If you are unable to get a successful DNS resolution, you must first address the issues with the DNS.

What are advanced DNS record lookup commands?

Typical DNS troubleshooting only considers whether or not there is an “A” record resolution of the domain. But it’s important to note that besides “A” records, DNS contains other types of records, such as MX, SOA, NS, etc., that provide ways to check the email routing, the actual ownership of the domain name, where the nameservers are located, and if the zones contain all of the information needed to run their DNS server.

Querying certain record types through nslookup allows you to troubleshoot issues with email delivery, verify DNS migrations, and validate domain configurations. As these commands allow you to perform advanced lookups, they are helpful tools for website owners, server administrators, and IT professionals managing their domains and hosting environments.

1. Check MX records

The Mail Exchange (MX) records identify the mail servers responsible for accepting emails sent to an address associated with a particular domain. When troubleshooting email reach issues, checking the MX records for the specific domain is the first step.

Email (MX Record) Lookup

2. Check TXT records

TXT records provide temporary or permanent text-based information related to DNS. It also serves other types of information and formats used for administrative purposes and verification of the domain owner or provider’s identity, which is stored with a TXT record.

TXT Record Lookup

3. Check NS records

The Nameserver (NS) records identify which DNS servers are responsible for managing the DNS zone for a domain.

Nameserver (NS) Lookup

4. Check SOA records

The Start of Authority (SOA) records contain the administrative information related to the primary authoritative nameserver for the DNS zone. It comprises major details required for zone administration.

SOA Record Lookup

How to reset DNS using CMD?

Using the command prompt to reset your DNS resolves multiple Internet issues like slow browsing, failed websites, and failed DNS queries. Each command is used to clear or refresh the various parts of your network configuration.

Below are the steps:

What are common DNS errors and the commands to fix them?

There are different ways that a DNS issue appears. Some cause a webpage loading failure or redirect to the wrong page, while others may prevent emails from loading. Below are some of the most common DNS problems and the CMD commands used to find or repair them.

1. Old website IP showing

2. Domain not resolving

3. DNS server configuration errors

4. Missing email records

5. Network stack damage

6. Issues with DNS Cache

What are the best practices when using DNS commands?

Using proper DNS troubleshooting procedures with the Command Prompt obtains accurate results and prevents unnecessary network problems.