IT Toolbox
Guide

How to know the DNS servers used on Windows

Identify DNS solvers actually configured on a Windows desktop.

TopicIT Networking →
⌚ About 2 min read
View my favorites
Network. Beginner 3 min

Identify DNS solvers actually configured on a Windows desktop.

Avant de commencer : adaptez toujours les commandes et manipulations à votre environnement. Sur un système de production, prévoyez une backup ou un retour arrière lorsque l’action peut modifier la configuration.

Étapes à suivre

  1. 1

    Open Power Shell

    Run Windows Terminal or Power Shell.

  2. 2

    Show DNS

    Use the Well-DnsClientServerAddress.

  3. 3

    Find the interface used

    Ignore disconnected interfaces and check Ethernet or Wi-Fi.

  4. 4

    Test resolution

    Use Resolve-DnsName to check that a name is correctly resolved.

Commands utiles

The new and updated version of the document is available on the website of the European Commission.
Resolve-Dns(1) boxinformatique.fr

À retenir

  • In an Active Directory domain, positions typically use the domain's internal DNS.
  • Avoid directly setting up a public DNS on a member post of an AD domain for no specific reason.
← All les guides
Technical deep dive

Windows addressing: useful reference points

Technical checkpoints

  • An address in 169.254.0.0/16 is APIPA: Windows did not obtain a usable DHCP
  • Read address, mask, gateway and DNS together: a correct IP with a wrong gateway or DNS is still a broken configuration.
  • Get-NetIPConfiguration gives a structured per-interface view; ipconfig /all remains useful for DHCP lease, DNS suffix and physical address.

Example check

Compare the active adapter, DHCP origin, gateway and DNS before renewing the lease.

Get-NetIPConfiguration
ipconfig /all

Topic-specific pitfalls

  • Renewing DHCP does not fix a wrong VLAN, an unauthorized switch port or a missing DHCP server.
  • A virtual or VPN adapter can appear before the interface actually in use: check InterfaceAlias and the default route.

How to validate

  • The address belongs to the expected subnet and no APIPA is present on the interface in use.
  • Gateway, DNS and DHCP lease match the expected network; the test is repeated after any change.
♡ 0