Get-DnsClientServerAddress
Use Get-DnsClientServerAddress to show the DNS servers configured per network interface.
Documentation: Microsoft Learn — PowerShell module reference
Syntax
See the command anatomy
Read the command and its supplied arguments. This example requires real PowerShell or its module; this diagram does not execute it.
Get-DnsClientServerAddress [[-InterfaceAlias] <string[]>] [-InterfaceIndex <UInt32[]>] [-AddressFamily <AddressFamily[]>] [-CimSession <CimSession[]>] [<CommonParameters>]- Stage 1Get-DnsClientServerAddress
-InterfaceAlias -InterfaceIndex -AddressFamily -CimSession
Try it
PowerShell example · browser support is limited.
Execution scope: The full example below requires PowerShell outside this browser. You can edit this runner to use the supported practice commands; unsupported syntax returns an explanation.
Follow the objects
Run the command to inspect each stage.
Examples
Get-DnsClientServerAddress -AddressFamily IPv4
Show reference output
Sample output · fictional data, shaped like the real thing
InterfaceAlias ServerAddresses -------------- ------------------------ Ethernet 10.20.30.10, 10.20.30.11 Wi-Fi
Filter by ServerAddresses
Show reference output
Sample output · fictional data, shaped like the real thing
InterfaceAlias AddressFamily ServerAddresses -------------- ------------- ------------------------ Ethernet IPv4 10.20.30.10, 10.20.30.11 Wi-Fi IPv4
Get-DnsClientServerAddress -InterfaceAlias Ethernet
Show reference output
Sample output · fictional data, shaped like the real thing
InterfaceAlias AddressFamily ServerAddresses -------------- ------------- ------------------------ Ethernet IPv4 10.20.30.10, 10.20.30.11 Wi-Fi IPv4
Parameters
Parameter definitions:
-InterfaceAlias-InterfaceIndex-AddressFamily-CimSession
Practical use and troubleshooting
Practical scenario: Use Get-DnsClientServerAddress when you need to show the DNS servers configured per network interface. Start with one identified target and inspect the returned values before extending the operation to a list. Keep the identity in your report so you can trace each result back to the object or path that produced it.
Common error and fix: No DNS servers on one interface may reflect a different address family or adapter. Select the intended interface and address family before changing DNS settings. In an unattended script, capture this failure with its original error record and record which target failed. An empty result and an unsuccessful query must remain distinguishable in the final report.
See also: Resolve-DnsName. Get-DnsClientServerAddress reads configured DNS server addresses; Resolve-DnsName performs a DNS query. Configuration alone does not establish that a server can answer the requested record. Read the linked command before substituting it; similar names do not imply identical inputs or output.
Recap
Get-DnsClientServerAddress Use Get-DnsClientServerAddress to show the DNS servers configured per network interface.
Next: Get-ADReplicationPartnerMetadata