大网数据广告活动
网络与域名解析

DNS server loses its NIC Teaming configuration

· 52CE 我爱测

Describes an issue in which a DNS server that's configured to use NIC Teaming reverts to using physical adapters after the computer restarts.

Applies to:   Windows Server 2019, Windows Server 2016

Symptoms

Consider the following scenario:

  • The DNS server computer has multiple network adapters that you use in a NIC Teaming configuration.
  • You configure the DNS server to listen on the IP address of the teaming network adapter.
  • On the Interfaces tab of the DNS server properties dialog box in DNS Manager, you can configure the IP address that you want to use.

In this scenario, when you set this configuration, Windows stores it in a registry value under the HKLM\SYSTEM\CurrentControlSet\Services\DNS\Parameters\ListenAddresses subkey.

After you restart the DNS server, Windows deletes both the setting and the registry value. The DNS server starts listening on all IP addresses again.

When this change occurs, Windows logs Event ID 410 in the DNS server event log:

The DNS server list of restricted interfaces does not contain a valid IP address for the server computer. The DNS server will use all IP interfaces on the machine. Use the DNS manager server properties, interfaces dialog, to verify and reset the IP addresses the DNS server should listen on. For more information, see "To restrict a DNS server to listen only on selected addresses" in the online Help.

Cause

As indicated by DNS Event ID 410, this behavior is expected.

When the DNS server starts, it checks the IP addresses of the available network adapters and notes that none of the addresses match the configured NIC Teaming address. Because of this mismatch, the DNS server determines that the configuration isn't valid. The DNS server then deletes the configuration, and reverts to listening on all available IP addresses.

NIC Teaming isn't available until after the physical adapters have come online. The issue occurs because the DNS Server service starts after the physical adapters come online. However, it doesn't wait for NIC Teaming adapter to become available.

Resolution

To resolve this issue, change the startup type of the DNS Server service to Automatic (Delayed Start). This setting delays the startup of the service so that the NIC Teaming adapter is available.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Server · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。