Enable DNS for DHCP-enabled clients
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
To enable DNS for DHCP-enabled clients
To configure DNS for clients with dynamically configured IP addresses provided by a DHCP server, you generally need to configure the following at either the DHCP server or applicable clients:
DNS host name (or names) for the client computer.
For DHCP clients, this must be set at the client computer or assigned during unattended setup.
Primary and alternate DNS servers that the client uses to assist in resolving DNS domain names.
For DHCP clients, this can be set by assigning the DNS server option (option 6) and providing a configured list of ordered IP addresses for the DNS servers that the client is configured to use.
A list of DNS suffixes to be appended for use in completing unqualified DNS names used for searching and submitting DNS queries at the client for resolution.
For DHCP clients, this can be set by assigning the DNS domain name option (option 15) and providing single DNS suffix for the client to append and use in searches. To configure additional DNS suffixes, configure TCP/IP manually for DNS configuration.
Connection-specific dynamic update and registration behavior, such as whether specific network adapters installed at the client dynamically register their configured IP addresses with a DNS server.
For DHCP clients, the default is for client connections to register their configured IP addresses with a DNS server. To modify this behavior at the client, configure TCP/IP manually for DNS configuration.
Performing this task does not require you to have administrative credentials. Therefore, as a security best practice, consider performing this task as a user without administrative credentials.
For more information on how to configure other DNS for DHCP clients, see the applicable TCP/IP or DNS documentation provided by the appropriate vendor.
By default, the DNS client on Windows XP does not attempt dynamic update over a Remote Access Service (RAS) or virtual private network connection. To modify this configuration, you can modify the advanced TCP/IP settings of the particular network connection or modify the registry. For more information, see Related Topics.
By default, the DNS client does not attempt dynamic update of top-level domain (TLD) zones. Any zone named with a single-label name is considered a TLD zone, for example, com, edu, blank, my-company. To configure the DNS client to allow the dynamic update of TLD zones, you can use the Update Top Level Domain Zones policy setting or modify the registry.
For more information about DHCP options, see "DHCP Options" at the Microsoft Windows Resource Kits Web site.
Information about functional differences
- Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings. For more information, see Viewing Help on the Web.