Windows 8 Client with a single DNS server configured, querying for In this scenario, the client is then trying to query the same DNS server five times before timing out. If no response is received after 2 more seconds, client stops queryingĪny Name Error response by the DNS server will cause the process to stop - client doesn't retry if the response was negative. If no response is received after 4 more seconds, client queries again the DNS server If no response is received after 2 more seconds, client queries again the DNS server If no response is received after 1 more second, client queries again the DNS server
If no response is received after 1 second, client queries again the DNS server The behavior is the following (tested on Windows XP, Windows 7, and Windows 8 clients with a single NIC): Time (seconds since start) What is the default behavior of a DNS client when a single DNS server is configured on the NIC Such name failures may cause application or component hangs, resource outages waiting for dependent timeout expirations that directly or indirectly cause operational failures.įor these reasons, it's recommended to configure any Windows client with more than one DNS server, but it's important to be aware of the Windows client resolution process, as it's different based on how many DNS servers we've configured. Adding multiple DNS Servers IPs allows DNS names to continue to be resolved if failures of the only configured DNS Server, of the underlying network link, or the supporting network infrastructure that connects a given client to a DNS Server. This document describes the fallback and timeout behavior that exist when one or more Domain Name System (DNS) Servers IPs are configured on a Windows DNS client.Īpplies to: Windows 10 - all editions Original KB number: 2834226 Summaryįor more information, see NET: DNS: Forwarders and Conditional Forwarders resolution timeouts.Ĭonfiguring DNS clients with more than one DNS Server IP adds additional fault tolerance to your DNS infrastructure.
0 kommentar(er)
