Dhcp clients not updating dns
In Windows 2000, clients can send dynamic updates for three different types of network adapters: DHCP adapters, statically configured adapters, and remote access adapters.
Regardless of which adapter is used, the DHCP client service sends dynamic updates to the authoritative DNS server.
However, Windows 2000 DHCP servers can perform dynamic updates on behalf of clients that do not support the FQDN option (which is described in the following section).
For example, clients that are running Windows 95, Windows 98, and Windows NT do not support the FQDN option.
This section describes the Windows 2000 implementation of dynamic update.
If you want to speed up the discovery of authoritative servers, you can configure each client with a list of preferred and alternate DNS servers that are authoritative for that directory-integrated zone.In some cases, stale PTR or A resource records can appear on DNS servers when the lease of a DHCP client expires.For example, when a Windows 2000 DHCP client tries to negotiate a dynamic update procedure with a Windows NT 4.0 DHCP server, the Windows 2000 DHCP client must register both A and PTR resource records itself.To prevent problems with stale PTR and A resource records, you can enable the aging and scavenging feature.For more information about the aging and scavenging feature, see "Aging and Scavenging" later in this chapter.The DHCP client service runs on all computers regardless of whether they are configured as DHCP clients.By default, the dynamic update client dynamically registers its A resource records and possibly all of its PTR resource records every 24 hours or whenever any of the following events occur: By default, the dynamic update client automatically deregisters name–to–IP address mappings whenever the DHCP lease expires.Table 6.6 lists the fields of the FQDN option of the DHCPREQUEST packet.Table 6.6 Fields in the FQDN Option of the DHCPREQUEST Packet The DHCP server uses these fields to specify the response code from an A resource record registration performed on the client's behalf and to indicate whether it attempted the update before sending DHCPACK.It also depends on and how the client is configured.Clients can take any of the following actions: Depending on what the client requests, the server can take different actions.