Microsoft windows 2000 DNS manual Mixed Environment, Dhcp Client

Page 23

The dynamic update algorithm differs depending on the type of client network adapter engaging in the dynamic update process. The following three scenarios will be examined:

DHCP client

Statically configured client

RAS client

DHCP Client

When a Windows 2000 DHCP client bootstraps, it negotiates the dynamic update procedure with a DHCP server. By default, the DHCP client always proposes that it update the A resource record, while the DHCP server updates the PTR resource record.

The Windows 2000 DHCP server can be configured to “Update DNS server according to client request” (default setting), or ”Always update forward and reverse look-ups.”

If the DHCP server is configured to Always update forward and reverse lookups, it will update both A and PTR RRs itself regardless of the DHCP client’s request.

If the DHCP server is disabled to perform dynamic updates, the DHCP client will attempt to update both A and PTR RRs itself.

At expiration of the IP address lease, these records must be removed from the appropriate zones. Dynamic cleanup requires that the records are deleted by the registering computer(s)—in this case the DHCP client or server or both—that created them. Thus, if the machine that created an A or PTR resource record is disconnected from the network before the lease expiration, the corresponding resource records may become stale. Since the DHCP server is the owner of the IP address it is encouraged that DHCP servers perform PTR records registration when possible.

Mixed Environment

It is possible that a Windows 2000 DHCP client will try to negotiate the dynamic update procedure with the Windows NT 4.0 DHCP server (or any other DHCP server that doesn’t support DNS dynamic updates). Since the Windows NT 4.0 DHCP server does not support dynamic updates, the Windows 2000 DHCP client will have to update both the A and PTR RRs itself.

In the reverse situation, with down-level clients (for example, Windows 95, Windows 98, and Windows NT 4.0), the Windows 2000 DHCP server after negotiation of a lease with a client, will register both the A and PTR records in DNS, if the ”Do updates for down-level DHCP clients” option is selected in a configuration of the DHCP server.

DHCP Server Considerations

In addition, when the DHCP client’s lease expires, the DHCP server will remove the

Windows 2000 White Paper

17

Image 23
Contents Windows 2000 DNS Microsoft Corporation. All rights reserved Contents Designing a DNS Namespace for the Active Directory Summary Page DNS Fundamentals Standards and Additional Reading Name Services in WindowsDraft-skwan-gss-tsig-04.txt GSS Algorithm for Tsig GSS-TSIG History of DNSHierarchy of DNS Domain Names Structure of DNSDNS and Internet Int/net/orgCom Edu Gov Mil Army Microsoft Mit MydomainDistributing the Database Zone Files and Delegation TTLMicrosoft My domain ftp Ntserver Replicating the DNS databaseQuerying the Database NEW Features of the Windows 2000 DNSName Server Resolver Root-server Gov Whitehouse.gov Time to Live for Resource Records Updating the DNS DatabaseActive Directory Storage and Replication Integration Active Directory Service Storage ModelWindows 2000 White Paper Zone Type Conversions Controlling Access to ZonesReplication Model Protocol Description Incremental Zone TransferSlave DNS Server Ixfr and DS Integration Dynamic UpdateZone Log File Master DNS ServerDynamic Update of DNS Records Update AlgorithmDhcp Client Mixed EnvironmentClient Reregistration Statically Configured ClientSecure Dynamic Update RAS ClientEstablishing a security context by passing security tokens Secure Dynamic Update Policy Controlling Update Access to Zones and Names DnsUpdateProxy GroupAging and Scavenging DNS Admins GroupAging and Scavenging Parameters DefaultEnableScavenging Scavenging Period DescriptionRecord Life Span Scavenging Algorithm Configuring Scavenging ParametersInteroperability Considerations Unicode Character SupportDomain Locator Finish IP/DNS Compatible Locator DNS Record Registration and Resolver RequirementsLdap.tcp.dc.msdcs.DnsDomainName Kerberos.tcp.dc.msdcs.DnsDomainName IP/DNS DC Locator Algorithm Finish Discovering Site specific DCsCaching Resolver Fully-Qualified Query Name ResolutionUnqualified Single-Label Query Using Global Suffix Search OrderUnqualified Multi-Label Query Using Primary and Per-adapter Domain NamesUnqualified Single-Label Query Scenarios Name Resolution ScenariosNegative Caching Fully-Qualified Query ScenariosMicrosoft Implementation of Negative Caching DNS Server List ManagementDNS Manager Administrative ToolsWMI Support for DNS Server Administration Using UTF-8 Characters Format Interoperability IssuesUsing Wins and Winsr Records Utilization DNS Server PerformanceReceiving Non-RFC Compliant Data Hardware components Sizing Server Capacity PlanningChoosing Names Internet Access ConsiderationsWindows 2000 White Paper Windows 2000 White Paper Windows 2000 White Paper VPN Com Yyy.com Zzz.com Windows 2000 White Paper Primary Zone YYY corporation ZZZ corporation VPN Firewall Computer Names Characters in NamesPer-Adapter Naming Full computer nameIntegrating ADS with Existing DNS Structure Domain name and sites. Active Directory domain name DNS Migration to Windows 2000 DNSPartitioning, and Replication Choosing your Zones Deploying DNS to Support Active DirectoryWins Referral Using Automatic ConfigurationIxfr Ixfr For More InformationWindows 2000 White Paper