Article ID: 275553 - View products that this article applies to.
This article was previously published under Q275553
NoticeThis article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center
(https://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fwin2000)is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy
This article describes how to automate the process of configuring the domain suffix search list on your Domain Name System (DNS) clients.
This article does not describe when it is necessary to configure the domain suffix search list on a client. This article only describes how to distribute a large-scale domain suffix search list.
The typical name resolution process for Microsoft Windows 2000 uses the primary DNS suffix and any connection-specific DNS suffixes. If these suffixes do not work, the devolution of the primary DNS suffix is attempted by the name resolution process.
When a domain suffix search list is configured on a client, only that list is used. The primary DNS suffix and any connection-specific DNS suffixes are not used, nor is the devolution of the primary suffix attempted. The domain suffix search list is an administrative override of all standard Domain Name Resolver (DNR) look-up mechanisms.
For more information about how DNS suffixes are used, go to Windows 2000 Help and view the Configuring Client Settings topic (located in the Networking/DNS/Concepts/Using DNS/Managing Clients/ folder).
Pushing the domain suffix search list to DNS clientsThe following methods of distribution are available for pushing the domain suffix search list to DNS clients:
Sample Regini scriptCreate a text file with the following two lines of text and save it as the Suffix.txt file. The following spacing must be exactly as shown, where adatum.xxx signifies a domain suffix. Up to six domain suffixes may be specified. The search order is left to right.
\Registry\Machine\System\CurrentControlSet\Services\TCPIP\ParametersCopy the Regini.exe and Suffix.txt files to the preceding location and run the regini.exe suffix.txt command.
When the script has updated the registry, you must restart the computer for the settings to be updated.
To run the script you must have administrator or system-level access to the computer.
Note Another method is to use Microsoft Windows Script Host:
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/312468/ )How to request additional DHCP options from a DHCP server
Article ID: 275553 - Last Review: March 1, 2007 - Revision: 5.7