Microsoft windows 2000 DNS manual Using Primary and Per-adapter Domain Names

Page 45

The query is processed as a fully-qualified query.

If the result is a positive response, the response is returned to the caller.

If the result is a timeout, then a timeout is returned to the caller.

If the result is a negative response, the next suffix is appended and the algorithm is restarted at step 2.

If the suffix search list is exhausted without success, then a negative response is returned to the caller.

Using Primary and Per-adapter Domain Names

A Windows 2000-based computer has a PrimaryDnsDomainName from the machine configuration. Each adapter may also have an IpDnsDomainName from its TCP/IP configuration.

The name concatenation algorithm in a name resolution process is as follows:

1.The PrimaryDnsDomainName is appended to the name.

2.The query is submitted as a fully-qualified query

If the result is a positive response, the response is returned to the client.

If the result is a timeout, then a timeout is returned to the client.

If the result is a negative response:

append to the original single-label name the IpDnsDomainName that has not been used yet from an adapter in the TCP/IP binding order, and the algorithm is restarted at step 2.

if all unique IpDnsDomainNames are exhausted, and the Registry flag for devolution is set, then the devolution algorithm is tried using the PrimaryDnsDomainName and the algorithm is restarted at step 2. Note that name devolution does not shrink primary domain name to less than a 2-label name (for example, microsoft.com.). Also note that the name devolution algorithm is not applicable to per-adapter (IpDnsDomainName) domain names.

The response is returned to the client.

The registry key for devolution is on by default to mirror the behavior of a Windows NT 4.0-based client. Administrators may turn it off through the Registry.

Unqualified Multi-Label Query

A name containing dots, but not dot-terminated, is called an Unqualified Multi-Label name, for example ntserver.mydomain. A name with dots in it may be unique, or partially qualified.

The name resolution algorithm for such names is as follows:

The query is submitted as a fully-qualified query (with the ntserver.mydomain. name).

If the result is a positive response, the response is returned to the client.

If the result is a timeout, then a timeout is returned to the client.

If the result is a negative response, then the query is submitted as an unqualified single-label query.

Windows 2000 White Paper

39

Image 45
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 DNSCom Edu Gov Mil Army Microsoft Int/net/orgMit Mydomain DNS and InternetDistributing 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 Controlling Access to Zones Replication ModelZone Type Conversions Protocol Description Incremental Zone TransferZone Log File Dynamic UpdateMaster DNS Server Slave DNS Server Ixfr and DS IntegrationDynamic Update of DNS Records Update AlgorithmDhcp Client Mixed EnvironmentSecure Dynamic Update Statically Configured ClientRAS Client Client ReregistrationEstablishing 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 ScenariosMicrosoft Implementation of Negative Caching Fully-Qualified Query ScenariosDNS Server List Management Negative CachingAdministrative Tools WMI Support for DNS Server AdministrationDNS Manager Interoperability Issues Using Wins and Winsr RecordsUsing UTF-8 Characters Format DNS Server Performance Receiving Non-RFC Compliant DataUtilization 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