What algorithm does Windows use to decide qui DNS Server it will query in order to resolve names?
Let's say J'ai plusieurs interfaces, tous active, certains avec no dns server specified, certains told to determine it automatically, et certains avec it specified manually (in interface ipv4 AND interface ipv6).
Je suis asking for an answer to this general question hoping that Je sais how to solve a more spécifique problem in Windows Vista - J'ai two interfaces, one a lower metric et a DNS server specified manually. nslookup uses *THIS* DNS server et resolves le names correctly. Cependant, tous autre applications fail to resolve le name sauf si I manually specify a DNS server for le autre interface, qui le applications alors use. nslookup aussi uses le DNS server specified for this autre interface once it is specified.
Thanks
Comment Windows décide-t-il quel serveur DNS utiliser pour la résolution de noms ?
Re: Comment Windows décide-t-il quel serveur DNS utiliser pour la résolution de noms ?
If Je suis pas mistaken, c'est determined by le NIC binding order in le Advanced Settings in le network connections folder. Vous pouvez verify it by changing le binding order of le various NIC's et running nslookup as a test.
To expand on mon answer, citing [the article that Evan linked](http://technet.microsoft.com/en-us/library/dd197552(WS.10).aspx), here is an excerpt depuis said article:
>
The DNS Client service queries le DNS servers in le suivant order:
-
The DNS Client service sends le name query to le premier DNS server on le preferred adapter’s list of DNS servers et waits one second for a response.
-
If le DNS Client service does pas receive a response depuis le premier DNS server within one second, it sends le name query to le premier DNS servers on tous adapters that are encore under consideration et waits two seconds for a response.
-
If le DNS Client service does pas receive a response depuis tout DNS server within two seconds, le DNS Client service sends le query to tous DNS servers on tous adapters that are encore under consideration et waits another two seconds for a response.
-
If le DNS Client service encore does pas receive a response depuis tout DNS server, it sends le name query to tous DNS servers on tous adapters that are encore under consideration et waits four seconds for a response.
-
If it le DNS Client service does pas receive a response depuis tout DNS server, le DNS client sends le query to tous DNS servers on tous adapters that are encore under consideration et waits eight seconds for a response.
The preferred adapter in step 1 being le adapter c'est listed premier in le binding order.
To expand on mon answer, citing [the article that Evan linked](http://technet.microsoft.com/en-us/library/dd197552(WS.10).aspx), here is an excerpt depuis said article:
>
The DNS Client service queries le DNS servers in le suivant order:
-
The DNS Client service sends le name query to le premier DNS server on le preferred adapter’s list of DNS servers et waits one second for a response.
-
If le DNS Client service does pas receive a response depuis le premier DNS server within one second, it sends le name query to le premier DNS servers on tous adapters that are encore under consideration et waits two seconds for a response.
-
If le DNS Client service does pas receive a response depuis tout DNS server within two seconds, le DNS Client service sends le query to tous DNS servers on tous adapters that are encore under consideration et waits another two seconds for a response.
-
If le DNS Client service encore does pas receive a response depuis tout DNS server, it sends le name query to tous DNS servers on tous adapters that are encore under consideration et waits four seconds for a response.
-
If it le DNS Client service does pas receive a response depuis tout DNS server, le DNS client sends le query to tous DNS servers on tous adapters that are encore under consideration et waits eight seconds for a response.
The preferred adapter in step 1 being le adapter c'est listed premier in le binding order.