Dns tool windows

Dns tool windows DEFAULT


Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012

Displays information that you can use to diagnose Domain Name System (DNS) infrastructure. Before using this tool, you should be familiar with how DNS works. The nslookup command-line tool is available only if you have installed the TCP/IP protocol.

The nslookup command-line tool has two modes: interactive and noninteractive.

If you need to look up only a single piece of data, we recommend using the non-interactive mode. For the first parameter, type the name or IP address of the computer that you want to look up. For the second parameter, type the name or IP address of a DNS name server. If you omit the second argument, nslookup uses the default DNS name server.

If you need to look up more than one piece of data, you can use interactive mode. Type a hyphen (-) for the first parameter and the name or IP address of a DNS name server for the second parameter. If you omit both parameters, the tool uses the default DNS name server. While using the interactive mode, you can:

  • Interrupt interactive commands at any time, by pressing CTRL+B.

  • Exit, by typing exit.

  • Treat a built-in command as a computer name, by preceding it with the escape character (). An unrecognized command is interpreted as a computer name.



nslookup exitExits the nslookup command-line tool.
nslookup fingerConnects with the finger server on the current computer.
nslookup helpDisplays a short summary of subcommands.
nslookup lsLists information for a DNS domain.
nslookup lserverChanges the default server to the specified DNS domain.
nslookup rootChanges the default server to the server for the root of the DNS domain name space.
nslookup serverChanges the default server to the specified DNS domain.
nslookup setChanges configuration settings that affect how lookups function.
nslookup set allPrints the current values of the configuration settings.
nslookup set classChanges the query class. The class specifies the protocol group of the information.
nslookup set d2Turns exhaustive Debugging mode on or off. All fields of every packet are printed.
nslookup set debugTurns Debugging mode on or off.
nslookup set domainChanges the default DNS domain name to the name specified.
nslookup set portChanges the default TCP/UDP DNS name server port to the value specified.
nslookup set querytypeChanges the resource record type for the query.
nslookup set recurseTells the DNS name server to query other servers if it doesn't have the information.
nslookup set retrySets the number of retries.
nslookup set rootChanges the name of the root server used for queries.
nslookup set searchAppends the DNS domain names in the DNS domain search list to the request until an answer is received. This applies when the set and the lookup request contain at least one period, but do not end with a trailing period.
nslookup set srchlistChanges the default DNS domain name and search list.
nslookup set timeoutChanges the initial number of seconds to wait for a reply to a request.
nslookup set typeChanges the resource record type for the query.
nslookup set vcSpecifies to use or not use a virtual circuit when sending requests to the server.
nslookup viewSorts and lists the output of the previous ls subcommand or commands.
  • If computerTofind is an IP address and the query is for an A or PTR resource record type, the name of the computer is returned.

  • If computerTofind is a name and doesn't have a trailing period, the default DNS domain name is appended to the name. This behavior depends on the state of the following set subcommands: domain, srchlist, defname, and search.

  • If you type a hyphen (-) instead of computerTofind, the command prompt changes to nslookup interactive mode.

  • If the lookup request fails, the command-line tool provides an error message, including:

    Error messageDescription
    timed outThe server didn't respond to a request after a certain amount of time and a certain number of retries. You can set the time-out period with the nslookup set timeout command. You can set the number of retries with the nslookup set retry command.
    No response from serverNo DNS name server is running on the server computer.
    No recordsThe DNS name server doesn't have resource records of the current query type for the computer, although the computer name is valid. The query type is specified with the nslookup set querytype command.
    Nonexistent domainThe computer or DNS domain name doesn't exist.
    Connection refused or Network is unreachableThe connection to the DNS name server or finger server could not be made. This error commonly occurs with the ls and finger requests.
    Server failureThe DNS name server found an internal inconsistency in its database and could not return a valid answer.
    RefusedThe DNS name server refused to service the request.
    format errorThe DNS name server found that the request packet was not in the proper format. It may indicate an error in nslookup.

Additional References

Sours: https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/nslookup

DNS Manager

There are a number of utilities for administering, monitoring, and troubleshooting both Domain Name System (DNS) servers and clients. These utilities include the following:

  • DNS Manager (DNS on the Administrative Tools menu).

  • Command-line utilities, such as Nslookup, which you can use to troubleshoot DNS problems.

  • Logging features, such as the DNS server log, which you can view by using DNS Manager or Event Viewer. You can also use file-based logs temporarily as an advanced debugging option to log and trace selected service events.

  • Performance-monitoring utilities, such as statistical counters to measure and monitor DNS server activity with System Monitor.

  • Windows Management Instrumentation (WMI), a standard technology for accessing management information in an enterprise environment.

  • Platform Software Developer Kit (SDK).

The primary tool that you use to manage DNS servers is DNS Manager, the DNS snap-in in Microsoft Management Console (MMC), which appears as DNS in Administrative Tools on the Start menu. You can use DNS Manager along with other snap-ins in MMC, further integrating DNS administration into your total network management. It is also available in Server Manager on computers with the DNS Server role installed.

You can use DNS Manager to perform the following basic administrative server tasks:

  • Performing initial configuration of a new DNS server.

  • Connecting to and managing a local DNS server on the same computer or remote DNS servers on other computers.

  • Adding and removing forward and reverse lookup zones, as necessary.

  • Adding, removing, and updating resource records in zones.

  • Modifying how zones are stored and replicated between servers.

  • Modifying how servers process queries and handle dynamic updates.

  • Modifying security for specific zones or resource records.

In addition, you can also use DNS Manager to perform the following tasks:

  • Perform maintenance on the server. You can start, stop, pause, or resume the server or manually update server data files.

  • Monitor the contents of the server cache and, as necessary, clear it.

  • Tune advanced server options.

  • Configure and perform aging and scavenging of stale resource records that are stored by the server.

In addition, you can also operate DNS Manager from a workstation to remotely administer DNS servers.


You can use DNS Manager only to manage DNS servers running Windows Server operating systems. The console cannot be used to manage other DNS servers, such as BIND servers.

There are several command-line utilities that you can use to manage and troubleshoot DNS servers and clients. The following table describes each of these utilities, which you can run either by typing them at a command prompt or by entering them in batch files for scripted use.



Performs query testing of the DNS domain namespace.


A command-line interface for managing DNS servers. This utility is useful in scripting batch files to help automate routine DNS management tasks or to perform simple unattended setup and configuration of new DNS servers on your network.


Displays and modifies IP configuration details that are used by the computer. Additional command-line options are included with this utility to provide help in troubleshooting and supporting DNS clients.

The Windows Server 2008 family includes two options for monitoring DNS servers:

  • Default logging of DNS server event messages to the DNS server log.

    DNS server event messages are separated and kept in their own system event log, the DNS server log, which you can view using DNS Manager or Event Viewer.

    The DNS server log contains events that are logged by the DNS Server service. For example, when the DNS server starts or stops, a corresponding event message is written to this log. Most additional critical DNS Server service events are also logged here, for example, when the server starts but cannot locate initializing data and zones or boot information stored in the registry or (in some cases) Active Directory Domain Services (AD DS).

    You can use Event Viewer to view and monitor client-related DNS events. These events appear in the System log, and they are written by the DNS Client service at any computers running Windows (all versions).

  • Optional debug options for trace logging to a text file on the DNS server computer.

    You can also use DNS Manager to selectively enable additional debug logging options for temporary trace logging to a text-based file of DNS server activity. The file that is created and used for this feature, Dns.log, is stored in the %systemroot%\System32\Dns folder.

You can do performance monitoring for DNS servers using additional service-specific counters that measure DNS server performance. These counters are accessible through System Monitor, which is provided in the Performance snap-in.

When you use System Monitor, you can create charts and graphs of server performance trends over time for any of your DNS servers. These can be further studied and analyzed to determine if additional server tuning is needed.

Through measurement and review of server metrics over a period of time, it is possible to determine performance benchmarks and decide if further adjustments can be made to optimize the system.

WMI is the Microsoft implementation of Web-Based Enterprise Management (WBEM), which is an industry initiative to develop a standard technology for accessing management information in an enterprise environment. WMI uses the Common Information Model (CIM) industry standard to represent systems, applications, networks, devices, and other managed components in an enterprise environment. For more information about WMI, see Windows Management Instrumentation (WMI) (http://go.microsoft.com/fwlink/?LinkID=80947).

Computers that run a product in the Windows Server 2008 family provide functions that make it possible for application programmers to use DNS, for example, programmatically making DNS queries, comparing records, and looking up names.

Programmable DNS components are designed for use by C/C++ programmers. Familiarity with networking and DNS is required. Programmers should be familiar with the IP protocol suite, as well as the DNS protocol and DNS operations.

Sours: https://winintro.ru/dnsmgr.en/html/412a919f-4249-4341-aecd-bdb35d266338.htm
  1. Practical knowledge synonyms
  2. 4x4 framing brackets
  3. Skyline construction llc
  4. Log cabin chronicles
  5. Pewdiepie buff

DNS Tools

Linux DNS Tools


dig command is one of the most useful dns utilities you will ever use, it's a fast tool for querying dns servers when you are looking for Address records, NameServer records, MX records (mail exchanger) and other types of dns records like SPF, DKIM, etc.

dig tool is available for Linux and Unix systems (including MacOS) . The most common usage of dig command on Linux is against a single host, for example to query local dns resolve response after dns propagation, as you see below

Example of dns query using dig command:

dig dnspropagation.net
Example output:

[[email protected] ~]$ dig NS dnspropagation.net ; <<>> DiG 9.11.1-P2-RedHat-9.11.1-2.P2.fc26 <<>> NS dnspropagation.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56121 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 5 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;dnspropagation.net. IN NS ;; ANSWER SECTION: dnspropagation.net. 78897 IN NS kay.ns.cloudflare.com. dnspropagation.net. 78897 IN NS duke.ns.cloudflare.com. ;; ADDITIONAL SECTION: kay.ns.cloudflare.com. 41948 IN A kay.ns.cloudflare.com. 47729 IN AAAA 2400:cb00:2049:1::adf5:3a7d duke.ns.cloudflare.com. 61899 IN A duke.ns.cloudflare.com. 71568 IN AAAA 2400:cb00:2049:1::adf5:3b6e ;; Query time: 90 msec ;; SERVER: ;; WHEN: mar sep 05 21:34:05 -03 2017 ;; MSG SIZE rcvd: 189

As you see on this example, dig was very useful to discover lot of information regarding the primary and secondary name servers used, as well as their main IP addresses.

If you want to use dig to know the IP of a certain IP the syntax would be the same:

dig A domain.com

Output example:

[[email protected] ~]$ dig A dnspropagation.net ; <<>> DiG 9.11.1-P2-RedHat-9.11.1-2.P2.fc26 <<>> A dnspropagation.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7713 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 5 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;dnspropagation.net. IN A ;; ANSWER SECTION: dnspropagation.net. 300 IN A

On this last dig command example, we've found additional details like the IP address of the remote domain name.


whois command is the most used WHOIS directory service client available on Linux and Unix.

whois is a terminal based utility that is used to search the WHOIS database when someone needs to find out information regarding domain names like domain registrar, domain name owner and dns nameservers used on the domain registrar.

whois command example to find out DNS Name Servers

[[email protected] ~]$ whois arin.net | grep "Name Server" -i Name Server: NS2.ARIN.NET Name Server: U.ARIN.NET Name Server: NS1.ARIN.NET Name Server: NS3.ARIN.NET [[email protected] ~]$ whois cloudflare.com | grep "Name Server" -i Name Server: NS3.CLOUDFLARE.COM Name Server: NS5.CLOUDFLARE.COM Name Server: NS4.CLOUDFLARE.COM Name Server: NS6.CLOUDFLARE.COM Name Server: NS7.CLOUDFLARE.COM


A dns lookup & reverse lookup tool for Unix and Linux systems.

host command is one of the most widely used dns utilities to perform reverse lookups, as well as normal dns lookups by system administrators.

The most common usage of host command is to know the host assigned to an IP address, as well as the opposite, to know the reverse IP information from a host.

host command examples

host domain.com or host IP

Host command output example:

[[email protected] ~]$ host dnspropagation.net dnspropagation.net has address dnspropagation.net mail is handled by 0 mail.dnspropagation.net. [[email protected] ~]$ host domain name pointer dnspropagation.net.

On this output you can see how the host dns tool is used to discover reverse dns (rDNS) assigned to the IP address, as well as the hostname IP response.


ping command is used to send ICMP ECHO_REQUEST to remote hosts across the network.

ping command is one of the top most used network commands by network administrators. ping utility is based on the ICMP ECHO_REQUEST datagram to answer against ICMP queries from remote hosts.

Ping examples to find our DNS records:

ping domain.com

Ping command output example:

[[email protected] ~]$ ping dnspropagation.net PING dnspropagation.net ( 56(84) bytes of data. --- dnspropagation.net ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms

While the ICMP response is closed on this server, we were able to use ping to determine the IP address of a domain name. Along with pinging domain names, ping command is also used to check network availablility and also to measure network response times.

Sours: https://dnspropagation.net/dns-tools/
How to setup a DNS Server on Windows
DNSDataView v1.61 - View the DNS records of specified domains
Copyright (c) 2008 - 2021 Nir Sofer

See Also


This utility is a GUI alternative to the NSLookup tool that comes with Windows operating system. It allows you to easily retrieve the DNS records (MX, NS, A, SOA) of the specified domains. You can use the default DNS server of your Internet connection, or use any other DNS server that you specify. After retrieving the DNS records for the desired domains, you can save them into text/xml/html/csv file.

System Requirements

DNSDataView can work on Windows XP, Windows Server 2003, Windows Vista, Windows 7, Windows Server 2008, Windows 8, and Windows 10. Older versions of Windows are not supported.

Versions History

  • Version 1.61:
    • Fixed bug: DNSDataView failed to work properly with IDN domains (Internationalized domain name) of some european languages.
  • Version 1.60:
  • Version 1.56:
    • Added /cfg command-line option to start DNSDataView with the specified config file.
  • Version 1.55:
    • You can now specify any variable inside DNSDataView.cfg as command-line option in order to modify the settings of DNSDataView, for example:
      DNSDataView.exe /NSRecords 1 /ARecords 1 /AAAARecords 1 /TEXTRecords 0
  • Version 1.50:
    • Added command-line options to export the result directly into a file without any user interface, for example:
      DNSDataView.exe /Domains "yahoo.com google.com" /scomma c:\temp\dns.csv
  • Version 1.46:
    • Fixed the domains text-box in 'Select Domains' window to handle Ctrl+A (Select All).
  • Version 1.45:
    • Added 'Automatically extract domains from URL' option. When it's turned on, you can enter a URL of a Web site, and DNSDataView will automatically extract the domain from the URL.
  • Version 1.43:
    • Fixed bug: When DNSDataView received multiple strings of TEXT DNS records, it displayed only the first one...
  • Version 1.42:
    • Added option to choose another font (name and size) to display in the main window.
  • Version 1.41:
    • Fixed the resizing problems of the 'Select Domains' window - some fields remained in their position instead of moving.
    • DNSDataView now remembers that last size and position of the 'Select Domains' window.
    • Fixed the tab order of the 'Select Domains' window.
  • Version 1.40:
    • Added 'Clear Windows DNS Cache' option, which allows you to easily clear the dns cache of Windows.
  • Version 1.35:
    • Added 'Load Windows DNS Cache' option, which displays the list of all DNS records stored in the DNS cache of Windows.
  • Version 1.31:
    • Fixed DNSDataView to work also on Windows 2000.
  • Version 1.30:
    • Added 'Get a PTR record for every IP address' option. When it's turned on, DNSDataView retrieves the PTR records of every IP address found in the other records.
  • Version 1.26:
    • When host name doesn't have IPv4 address, DNSDataView now retrieves its IPv6 address.
  • Version 1.25:
    • Added support for reverse DNS lookup (PTR records). You can now type a valid IP address instead of domain name, and DNSDataView will automatically make a reverse DNS lookup for the specified IP address, by sending the right PTR request.
  • Version 1.20:
    • Added 'Section' column which displays Answer or Additional.
    • Added option to fileter out additional records.
    • Fixed the resize problem of the SRV check box.
  • Version 1.15:
    • Added support for IDN domains (Internationalized domain name). When you type a domain name with non-English characters, DNSDataView automatically converts it to its Ascii form and then submit it to the DNS server.
  • Version 1.10:
    • Added support for SRV records.
  • Version 1.08:
    • Fixed bug: DNSDataView stopped displaying the IP addresses after adding the error information feature in v1.07.
  • Version 1.07:
    • Added new option : 'Show error information when DNS record cannot be retrieved'. When this option is turned on, DNSDataView will show error number and message for every DNS record that cannot be retrieved.
  • Version 1.06:
    • Added 'Add Header Line To CSV/Tab-Delimited File' option. When this option is turned on, the column names are added as the first line when you export to csv or tab-delimited file.
  • Versions 1.05:
    • Added support for AAAA records (IPv6). This feature might not work on Windows XP without installed service packs.
  • Versions 1.03:
    • Fixed issue: DNSDataView failed to get A record of host name, when the 'NS' option was selected too.
  • Versions 1.02:
    • Added accelerator key for DNS Options window (F9).
  • Versions 1.01:
    • Fixed bug: On Multi-monitor systems, the 'Select Domains' window always opened in the middle of the 2 monitors.
  • Versions 1.00 - First release.

Using DNSDataView

DNSDataView doesn't require any installation process or additional DLL files. In order to start using it, simply run the executable file - DNSDataView.exe
After running it, you can type one or more domains that you wish to view their DNS information, and click 'Ok'. After very short time, you should get all DNS records of the specified domains in the main window of DNSDataView.
If DNSDataView fails to retrieve the DNS records, you should try to manually type the DNS server of your Internet provider.

Command-Line Options

/Domains <Domains List> Specifies one or more domains to export their DNS information into text/html/xml file.
/stext <Filename> Save the DNS records list into a simple text file.
/stab <Filename> Save the DNS records list into a tab-delimited text file.
/scomma <Filename> Save the DNS records list into a comma-delimited text file (csv).
/stabular <Filename> Save the DNS records list into a tabular text file.
/shtml <Filename> Save the DNS records list into HTML file (Horizontal).
/sverhtml <Filename> Save the DNS records list into HTML file (Vertical).
/sxml <Filename> Save the DNS records list into XML file.
/cfg <Filename> Start DNSDataView with the specified configuration file. For example:
DNSDataView.exe /cfg "c:\config\ddv.cfg"
DNSDataView.exe /cfg "%AppData%\DNSDataView.cfg"
/ARecords <0 | 1>
/AAAARecords <0 | 1>
/CNAMERecords <0 | 1>
/MXRecords <0 | 1>
/SOARecords <0 | 1>
You can specify any variable inside DNSDataView.cfg as command-line option in order to modify the settings of DNSDataView, for example:
DNSDataView.exe /MXRecords 0 /ARecords 1 /AAAARecords 1 /SOARecords 0

DNSDataView.exe /Domains "yahoo.com google.com" /scomma c:\temp\dns.csv

Translating DNSDataView to other languages

In order to translate DNSDataView to other language, follow the instructions below:
  1. Run DNSDataView with /savelangfile parameter:
    DNSDataView.exe /savelangfile
    A file named DNSDataView_lng.ini will be created in the folder of DNSDataView utility.
  2. Open the created language file in Notepad or in any other text editor.
  3. Translate all string entries to the desired language. Optionally, you can also add your name and/or a link to your Web site. (TranslatorName and TranslatorURL values) If you add this information, it'll be used in the 'About' window.
  4. After you finish the translation, Run DNSDataView, and all translated strings will be loaded from the language file.
    If you want to run DNSDataView without the translation, simply rename the language file, or move it to another folder.


This utility is released as freeware. You are allowed to freely distribute this utility via floppy disk, CD-ROM, Internet, or in any other way, as long as you don't charge anything for this. If you distribute this utility, you must include all files in the distribution package, without any modification !


The software is provided "AS IS" without any warranty, either expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The author will not be liable for any special, incidental, consequential or indirect damages due to loss of data or any other reason.


If you have any problem, suggestion, comment, or you found a bug in my utility, you can send a message to [email protected]

DNSDataView is also available in other languages. In order to change the language of DNSDataView, download the appropriate language zip file, extract the 'dnsdataview_lng.ini', and put it in the same folder that you Installed DNSDataView utility.

Sours: https://www.nirsoft.net/utils/dns_records_viewer.html

Tool windows dns

“dig” is a robust command-line tool developed by BIND for querying DNS nameservers. It can identify IP address records, record the query route as it obtains answers from an authoritative nameserver, diagnose other DNS problems.

NOTE: Windows users can download the tool from BIND’s website. Use Terminal to access dig on Linux and Macintosh systems.

Accessing dig (Mac)

1. From your Applications folder, open the Utilities folder and select Terminal.digguide_02
2. When Terminal is open, type in any of the commands listed below using a hostname you wish to look up.digguide_03

Install dig (Windows)

1. Go to BIND’s website and download the most current, stable version of BIND.

NOTE: BIND supports both 32 and 64 bit Windows systems. Confirm which version of Windows you are using and download the correct version of BIND. View Microsoft’s documentation to determine which version of Windows you are using.

2. Extract the downloaded file and install BIND in the following directory: C:\Program Files\ISC BIND 9. Check the box beside Tools Only.digguide_win_5
3. Once BIND is installed, click on the Windows menu and open the Control Panel, then open System Properties.digguide_win_6_12
4. On the Advanced tab, click Environment Variables. Under System Variables, select Path and then click Edit.digguide_win_6_13
5. Scroll to the end of the path in the Edit System Variable window and add “C:\Program Files\ISC BIND 9\bin” to the end of the path. Then click OK.digguide_win_6_2
6. Click OK in the Edit Variables window and click OK in the System Properties window.
7. Access dig by opening the Command Prompt.
  • Windows 8-10:
    • Click the Windows menu icon.
    • Type in CMD into the Search field.
    • Click on Command Prompt.
  • Windows 7:
    • Go to the Start menu and click Run.
    • Type in CMD into the field and click OK.

Before using BIND’s dig tool, it is important to understand the components of a hostname.

In the diagram above, dyn.com is a domain root and a hostname with a specific set of records attached to it. www.dyn.com is a domain with a label or node added to the front of it, and constitutes as a different hostname with a separate set of records than dyn.com.

Another example of a hostname with a node would be help.dyn.com.

How to use dig

1. Open Terminal (Mac and Linux) or Command Prompt (Windows).
2. Type in dig (any hostname) and press enter.
3. Several pieces of information will be returned.


Understanding the Results


QUESTION SECTION: The query made to the DNS. In this example, we asked for the first available A record for the hostname, dyn.com.

ANSWER SECTION: The first available answer for the query made to the DNS. In this example, we received the A record for the IP address

AUTHORITY SECTION: The authoritative nameservers from which the answer to the query was received. These nameservers house the zones for a domain.

ADDITIONAL SECTION: Additional information the resolver may need but not the answer to the query.

dig Commands

Returns any A record found within the queried hostname’s zone.
Returns the records of that type found within the queried hostname’s zone. List of Record Types.
Provides a terse answer, usually just an IP address.
Queries the nameserver directly instead of your ISP’s resolver.
Adding instructs dig to resolve the query from the root nameserver downwards and to report the results from each query step.
Reverse lookup for IP addresses.
Returns all records for a hostname.
Sours: https://help.dyn.com/how-to-use-binds-dig-tool/
Установка и настройка DNS на Windows Server 2016 (Installing and adjustment DNS on Server 2016)


Similar news:


154 155 156 157 158