DNSServerSearchOrder

DNSServerSearchOrder specifies a list of IP addresses to use when searching for the DNS server on the network.

When running unattended setup for a DNS client, you can configure a list of suffixes for the DNS client to search and a list of DNS servers to use.

However, the entries are not guaranteed to be applied in any specific order.

To ensure the correct ordering of DNS servers, use Key in DNSServerSearchOrder and Key in DNSSuffixSearchOrder to specify the order in which each DNS server should be searched. For example,

   <DNSServerSearchOrder>
      <IpAddress wcm:action="add" wcm:keyValue="2">2001:4898:28:4:213:20ff:fe16:3e96</IpAddress>
      <IpAddress wcm:action="add" wcm:keyValue="3">173.145.1.12</IpAddress>
      <IpAddress wcm:action="add" wcm:keyValue="1">192.168.1.1</IpAddress>
   </DNSServerSearchOrder>

You can also use the Key setting under DNSSuffixSearchOrder element to ensure that suffixes are searched in a specific order. For example,

   <DNSSuffixSearchOrder>
      <DomainName wcm:action="add" wcm:keyValue="2">fabrikam.com</DomainName>
      <DomainName wcm:action="add" wcm:keyValue="3">server2.fabrikam.com</DomainName>
      <DomainName wcm:action="add" wcm:keyValue="1">server1.fabrikam.com</DomainName>    
      </ DNSSuffixSearchOrder >

For both of these examples, the value for Keyin DNSServerSearchOrder and Key in DNSSuffixSearchOrder indicates the order in which the DNS servers are searched. In this example, the server search order list is:

  1. 192.168.1.1
  2. 2001:4898:28:4:213:20ff:fe16:3e96
  3. 173.145.1.12

The suffix search order is:

  1. server1.fabrikam.com
  2. fabrikam.com
  3. server2.fabrikam.com

The value for Keyin DNSServerSearchOrder and Key in DNSSuffixSearchOrder must be unique, and can be set to any alphanumeric character. If the value is numeric (contains only numbers), these will be applied to order the list of IpAddress within DNSServerSearchOrder.

Child Elements

IpAddress

Specifies an IP address.

Parent Hierarchy

Microsoft-Windows-DNS-Client | Interfaces | Interface | DNSServerSearchOrder

Valid Passes

specialize

Applies To

For the list of the supported Windows editions and architectures that this component supports, see Microsoft-Windows-DNS-Client.

XML Example

The following XML output shows a DNS domain configuration for Fabrikam.

   <DNSDomain>fabrikam.com</DNSDomain>
   <DNSSuffixSearchOrder>
      <DomainName wcm:action="add" wcm:keyValue="1">server1.fabrikam.com</DomainName>
      <DomainName wcm:action="add" wcm:keyValue="2">fabrikam.com</DomainName>
   </DNSSuffixSearchOrder>
   <UseDomainNameDevolution>true</UseDomainNameDevolution>
   <Interfaces>
      <Interface wcm:action="add">
         <Identifier>Local Area Connection</Identifier>
         <DNSDomain>fabrikam.com</DNSDomain>
         <DNSServerSearchOrder>
            <IpAddress wcm:action="add" wcm:keyValue="1">192.168.1.1</IpAddress>
            <IpAddress wcm:action="add" wcm:keyValue="2">192.168.1.2</IpAddress>
         </DNSServerSearchOrder>
         <EnableAdapterDomainNameRegistration>true</EnableAdapterDomainNameRegistration>
         <DisableDynamicUpdate>false</DisableDynamicUpdate>
      </Interface>
      <Interface wcm:action="add">
         <Identifier>Local Area Connection 2</Identifier>
         <DNSDomain>fabrikam.com</DNSDomain>
         <DNSServerSearchOrder>
            <IpAddress wcm:action="add" wcm:keyValue="1">192.168.1.1</IpAddress>
            <IpAddress wcm:action="add" wcm:keyValue="2">2001:4898:28:4:213:20ff:fe16:3e96</IpAddress>
         </DNSServerSearchOrder>
         <EnableAdapterDomainNameRegistration>true</EnableAdapterDomainNameRegistration>
        <DisableDynamicUpdate>false</DisableDynamicUpdate>
      </Interface>
   </Interfaces>

See Also

Concepts

Interface