Export (0) Print
Expand All
Expand Minimize

Test-DnsServer

Windows Server 2012 R2 and Windows 8.1

Updated: May 20, 2014

Applies To: Windows 8.1, Windows PowerShell 4.0, Windows Server 2012 R2

Test-DnsServer

Tests that a specified computer is a functioning DNS server.

Syntax

Parameter Set: Context
Test-DnsServer [-IPAddress] <IPAddress[]> [[-Context] <String> ] [-AsJob] [-CimSession <CimSession[]> ] [-ComputerName <String> ] [-ThrottleLimit <Int32> ] [ <CommonParameters>]

Parameter Set: ZoneMaster
Test-DnsServer [-IPAddress] <IPAddress[]> -ZoneName <String> [-AsJob] [-CimSession <CimSession[]> ] [-ComputerName <String> ] [-ThrottleLimit <Int32> ] [ <CommonParameters>]




Detailed Description

The Test-DnsServer cmdlet tests whether a computer is a functioning Domain Name System (DNS) server. The DNS server must be running Windows Server® 2008 R2 operating system or above.

When you specify a computer by its IP address only, the cmdlet tests whether the computer is a DNS server. If you also specify a zone name, the cmdlet validates that the DNS server can resolve the specified zone.

Parameters

-AsJob

Runs the cmdlet as a background job. Use this parameter to run commands that take a long time to complete. The cmdlet immediately returns an object that represents the job and then displays the command prompt. You can continue to work in the session while the job completes. To manage the job, use the *-Job cmdlets. To get the job results, use the Receive-Job cmdlet. For more information about Windows PowerShell® background jobs, see about_Jobs.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-CimSession<CimSession[]>

Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session object, such as the output of a New-CimSession or Get-CimSession cmdlet. The default is the current session on the local computer.


Aliases

Session

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-ComputerName<String>

Specifies a DNSserver. The acceptable values for this parameter are:  an IP V4 address; an IP V6 address; any other value that resolves to an IP address, such as a fully qualified domain name (FQDN), host name, or NETBIOS name.


Aliases

Cn

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Context<String>

Specifies functionalities to test. Valid values are: DnsServer, Forwarder , and RootHints.


Aliases

none

Required?

false

Position?

3

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-IPAddress<IPAddress[]>

Specifies an array of DNS server IP addresses.


Aliases

none

Required?

true

Position?

2

Default Value

none

Accept Pipeline Input?

True (ByPropertyName)

Accept Wildcard Characters?

false

-ThrottleLimit<Int32>

Specifies the maximum number of concurrent operations that can be established to run the cmdlet. If this parameter is omitted or a value of 0 is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer. The throttle limit applies only to the current cmdlet, not to the session or to the computer.


Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-ZoneName<String>

Specifies the name of the zone that the server hosts.


Aliases

none

Required?

true

Position?

named

Default Value

none

Accept Pipeline Input?

True (ByPropertyName)

Accept Wildcard Characters?

false

<CommonParameters>

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see    about_CommonParameters.

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

Outputs

The output type is the type of the objects that the cmdlet emits.

Examples

Example 1: Test whether a DNS server is functional

This command tests whether the computer that has an IP address of 10.123.183.155 is a functional DNS server.


PS C:\> Test-DnsServer -IPAddress "10.123.183.155"
IPAddress               Result                  RoundTripTime           TcpTried                UdpTried
--------- -------- ------------ -------- --------
10.123.183.155 Success 00:00:11 True True

Example 2: Test whether a DNS server is functional and has valid configured forwarders

This command tests whether the computer that has an IP address of 10.123.183.155 is a functional DNS server that has valid configured forwarders.


PS C:\> Test-DnsServer -IPAddress "10.123.183.155" -Context Forwarder
IPAddress               Result                  RoundTripTime           TcpTried                UdpTried
--------- -------- ------------ -------- --------
10.123.183.155 Success 00:00:11 True True

Example 3: Test whether a DNS server is functional and has valid configured root hints

This command tests whether the computer that has an IP address of 10.123.183.155 is a functional DNS server that has valid configured root hints.


PS C:\> Test-DnsServer -IPAddress "10.123.183.155" -Context RootHints
IPAddress               Result                  RoundTripTime           TcpTried                UdpTried
--------- -------- ------------ -------- --------
10.123.183.155 NoResponse 00:00:12 False True

Example 4: Test whether a DNS server is functional and hosts the Contoso.com zone

This command tests whether the computer that has an IP address of 10.123.183.155 is a functional DNS server that hosts the Contoso.com zone.


PS C:\> Test-DnsServer -IPAddress "10.123.183.155" -ZoneName "Contoso.com"
IPAddress               Result                  RoundTripTime           TcpTried                UdpTried
--------- -------- ------------ -------- --------
10.123.183.155 Success 00:00:00 False True

Related topics

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft