Article ID: 934541 - View products that this article applies to.
The Dynamic Host Configuration Protocol for Internet Protocol version 6 (DHCPv6) option to support the connection-specific suffix search list for IPv6 is included in Windows Vista Service Pack 1 (SP1). The connection-specific suffix search list for IPv6 provides a reliable, flexible, and seamless name resolution experience in environments that consist of many domains.
In IPv4, Group Policy is used to enforce a suffix search list for all adapters. However, a suffix search list cannot be configured for each network adapter in IPv4. The DHCPv6 option to support a connection-specific suffix search list for IPv6 enables dynamic configuration of a suffix search list by using a DHCPv6 server. This option is also designed to fine-tune the configuration for each network adapter.
The Internet Engineering Task Force (IETF) standards body added the DHCPv6 option to support the connection-specific suffix search list for IPv6. The IETF standard is documented in Request for Comments (RFC) 3646. To view RFC 3646, visit the following RFC Web site:
http://www.rfc-editor.org/The DHCPv6 option to support the connection-specific suffix search list for IPv6 can be used. This option autoconfigures client computers so that they use a set of suffixes to complete Domain Name System (DNS) searches. The client computers do not have to be joined to a domain.
This DHCPv6 option is useful in environments that use single-label name resolution. Single-label name resolution refers to a scenario in which only the first label, the computer's host name, is used to resolve a name. Typically, single-label name resolution scenarios use suffixes that are configured on a client computer. The suffixes are appended to the single-label name on the client computer before name resolution is completed by using a DNS server. If a computer is not joined to a domain, the computer cannot be configured to automatically obtain a list of suffixes to use for DNS name resolution. This may be an issue in virtual private network (VPN) scenarios in which a client computer tries to connect to a corporate resource. In this scenario, a suffix search list is more suitable than a single connection-specific suffix because large organizations typically use many domains and forests.
If Windows Internet Name Service (WINS) and IPv4 are available, WINS can be used to resolve single-label name queries across a deployment. However, WINS will eventually become a legacy component, and it will be removed from future products. The connection-specific suffix search list for IPv6 lets a DHCPv6 server autoconfigure client computers whether they are joined to a domain or not. To do this, the DHCPv6 server uses a set of suffixes to complete DNS searches, especially searches for single-label names. A suffix search list works better than a single connection-specific suffix.
Use the connection-specific suffix search list to resolve connection issuesSingle-label name resolution may not be completed as expected when the following configurations are used:
When a computer that is running the DNS Client is restarted, the DNS Client performs a routine check for configuration changes. (These checks occur every 15 minutes.) If the DNS Client detects a configuration change, each network adapter is assigned suffixes as follows:
When a name is queried, the following process occurs.
Note Group Policy settings take precedence over local, manually configured suffixes or over DHCP-configured suffixes.
Article ID: 934541 - Last Review: May 15, 2007 - Revision: 1.5