How to Configure Duplicate Address Detection (DAD) and NUD in Windows 11 Using PowerShell

In modern computer networking, ensuring that IP addresses are unique across a local broadcast domain is critical for avoiding network outages and routing disruption. Both IPv4 (via Gratuitous ARP / RFC 5227) and IPv6 (via Neighbor Discovery Protocol / RFC 4862) implement Duplicate Address Detection (DAD). When a network interface is assigned an IP address, the operating system broadcasts query probes to verify that no existing host on the link is already using that address before marking the address as valid and usable.

Alongside DAD, Neighbor Unreachability Detection (NUD) actively monitors the reachability of adjacent nodes and default gateways. While these algorithms provide critical protection against address collisions, default Windows settings can introduce delays in high-availability environments—such as failover clustering, virtual machine provisioning, or rapid network reconnection—where waiting for DAD probes delays network binding. In Windows 11, administrators and systems engineers can inspect and fine-tune DAD transmits and NUD profiles directly using the NetTCPIP PowerShell module.

Understanding Duplicate Address Detection and NUD Mechanics

When an IP address is assigned to a Windows network interface (whether through static configuration, DHCP, or IPv6 stateless autoconfiguration SLAAC), the address enters a Tentative state:

• DAD Probes (DadTransmits): The host broadcasts a series of Neighbor Solicitation (NS) messages for IPv6 or ARP request probes for IPv4 targeting the tentative address. The parameter DadTransmits specifies how many probe packets are sent (default is typically 3 for IPv6 and 1 for IPv4).
• Tentative State Resolution: If no Neighbor Advertisement (NA) or ARP reply is received within the retransmission window (typically 1 second per transmit), the address transitions from Tentative to Preferred, and applications can begin binding sockets to it. If another host responds, Windows flags the address as duplicate, records Event ID 4199 in the System log, and disables the IP address.
• Neighbor Unreachability Detection (NUD): Periodically probes cached neighbor entries (in the ARP/Neighbor cache) to verify bidirectional reachability. If probes fail, the entry moves from Reachable to Stale, Delay, and finally Probe before being evicted.

Auditing Active DAD and Interface Properties in PowerShell

To inspect the current DAD configuration and neighbor discovery settings across all network adapters on Windows 11, launch an elevated PowerShell console and execute Get-NetIPInterface:

# Inspect DAD transmits and NUD properties across all network adapters
Get-NetIPInterface | Select-Object InterfaceAlias, AddressFamily, DadTransmits, NudProfile, InterfaceMetric

To target a specific physical network adapter (for example, “Ethernet”):

# Query detailed IP interface properties for Ethernet
Get-NetIPInterface -InterfaceAlias "Ethernet" | Format-List InterfaceAlias, AddressFamily, DadTransmits, NudProfile, RouterDiscovery, AutomaticMetric

Notice that Windows maintains distinct IP interface objects for IPv4 and IPv6 on the same physical adapter. Inspecting DadTransmits shows the configured probe count.

Configuring DAD Transmits for High-Availability Environments

In virtualized test environments, container networks, or high-availability failover nodes where static IP addresses are strictly managed by orchestration engines, you may need to reduce DAD transmits to minimize link initialization latency:

# Reduce DAD transmits to 1 probe on IPv6 for faster link readiness
Set-NetIPInterface -InterfaceAlias "Ethernet" -AddressFamily IPv6 -DadTransmits 1

To completely disable DAD probes (useful on isolated point-to-point links or simulated network namespaces where address uniqueness is guaranteed):

# Disable DAD probing on IPv6
Set-NetIPInterface -InterfaceAlias "Ethernet" -AddressFamily IPv6 -DadTransmits 0

Conversely, in lossy wireless environments or noisy industrial networks where packet drops are common, increasing DAD transmits prevents accidental address conflicts:

# Increase DAD probes to 5 for lossy network environments
Set-NetIPInterface -InterfaceAlias "Wi-Fi" -AddressFamily IPv6 -DadTransmits 5

Configuring Neighbor Unreachability Detection (NUD) Profiles

Windows 11 supports configurable NUD profiles that govern how aggressively the operating system probes neighbor gateways and stale cache entries. The NudProfile property accepts three primary profiles:

• Default: Standard operational profile for typical enterprise and home networks.
• LowLatency: Probes neighbors more frequently and transitions rapidly to probe states, minimizing failover detection time for latency-sensitive applications.
• Persistent: Designed for low-power or mobile environments, reducing neighbor solicitation broadcasts to conserve wireless energy.

To configure the low-latency NUD profile on an adapter connected to a dedicated storage or clustering subnet:

# Set NUD profile to LowLatency for fast gateway failure detection
Set-NetIPInterface -InterfaceAlias "Ethernet" -NudProfile LowLatency

To revert back to the standard operating system behavior:

# Restore default NUD profile
Set-NetIPInterface -InterfaceAlias "Ethernet" -NudProfile Default

Verifying Address State Transitions After Configuration

To confirm that your changes are functioning properly, assign an IP address or toggle the network interface, and query the address status using Get-NetIPAddress:

# Query IP address status and duplicate address flags
Get-NetIPAddress -InterfaceAlias "Ethernet" | Select-Object IPAddress, AddressFamily, AddressState, SkipAsSource

The AddressState property should report Preferred rather than remaining in Tentative, confirming that DAD verification completed successfully.

Tuning DAD transmits and NUD profiles via PowerShell allows Windows 11 systems engineers to eliminate link initialization bottlenecks, harden address validation, and optimize network responsiveness across diverse physical and virtual infrastructures.