Microsoft windows 2000 DNS manual Using Global Suffix Search Order, Unqualified Single-Label Query

Page 44

resolution. The following summarizes the name resolution algorithm:

The query is issued to the lead server on the preferred adapter's server list.

If no response was received within a one second interval, the query is issued to the lead server(s) on all lists, including the one on the preferred adapter.

If no response was received within a two second interval, the query is issued to all DNS servers on all lists, including the lead servers queried before.

If no response was received within a two second interval, once again the query is issued to all DNS servers on all lists.

This procedure will be repeated after 4 seconds, and later after 8 seconds if no response is received.

If the query is not resolved after all listed attempts (they may take up to seventeen seconds), then a timeout is returned to the client.

The algorithm is modified if some response(s) was received:

If a positive response is received from a server, the response is returned to the caller and the algorithm stops

If a negative response is received from a server, the list that server belongs to is removed from this query.

If a server on every adapter list returns a negative response, then a negative response is returned to the caller.

If a server returns a server failure, then that server is removed from the query for a certain period of time as described in the “DNS Server List Management” section.

Unqualified Single-Label Query

A name containing no dots is called an Unqualified Single-Label name, for example ntserver.

If such a name needs to be resolved it must be fully-qualified using some suffix before being placed on the wire. The list of suffixes to try can come from two places:

Global suffix search order, and

Primary and per-adapter domain names.

If a suffix search order is predefined, then it is used. If it is not defined then the Primary and per-adapter domain names are used.

Using Global Suffix Search Order

The global suffix search order is set by means of the TCP/IP configuration User Interface. It is not a per-adapter value. Suffixes are appended in the order given in the user interface.

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

The first suffix in the search order is appended to the name.

Windows 2000 White Paper

38

Image 44
Contents Windows 2000 DNS Microsoft Corporation. All rights reserved Contents Designing a DNS Namespace for the Active Directory Summary Page DNS Fundamentals Name Services in Windows Standards and Additional ReadingHistory of DNS Draft-skwan-gss-tsig-04.txt GSS Algorithm for Tsig GSS-TSIGStructure of DNS Hierarchy of DNS Domain NamesInt/net/org Com Edu Gov Mil Army MicrosoftMit Mydomain DNS and InternetTTL Distributing the Database Zone Files and DelegationReplicating the DNS database Microsoft My domain ftp NtserverNEW Features of the Windows 2000 DNS Querying the DatabaseName Server Resolver Root-server Gov Whitehouse.gov Updating the DNS Database Time to Live for Resource RecordsActive Directory Service Storage Model Active Directory Storage and Replication IntegrationWindows 2000 White Paper Zone Type Conversions Controlling Access to ZonesReplication Model Incremental Zone Transfer Protocol DescriptionDynamic Update Zone Log FileMaster DNS Server Slave DNS Server Ixfr and DS IntegrationUpdate Algorithm Dynamic Update of DNS RecordsMixed Environment Dhcp ClientStatically Configured Client Secure Dynamic UpdateRAS Client Client ReregistrationEstablishing a security context by passing security tokens Secure Dynamic Update Policy DnsUpdateProxy Group Controlling Update Access to Zones and NamesDNS Admins Group Aging and ScavengingAging and Scavenging Parameters DefaultEnableScavenging Description Scavenging PeriodRecord Life Span Configuring Scavenging Parameters Scavenging AlgorithmUnicode Character Support Interoperability ConsiderationsDomain Locator Finish DNS Record Registration and Resolver Requirements IP/DNS Compatible LocatorLdap.tcp.dc.msdcs.DnsDomainName Kerberos.tcp.dc.msdcs.DnsDomainName IP/DNS DC Locator Algorithm Discovering Site specific DCs FinishCaching Resolver Name Resolution Fully-Qualified QueryUsing Global Suffix Search Order Unqualified Single-Label QueryUsing Primary and Per-adapter Domain Names Unqualified Multi-Label QueryName Resolution Scenarios Unqualified Single-Label Query ScenariosFully-Qualified Query Scenarios Microsoft Implementation of Negative CachingDNS Server List Management Negative CachingDNS 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 Server Capacity Planning Hardware components SizingInternet Access Considerations Choosing NamesWindows 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 Characters in Names Computer NamesFull computer name Per-Adapter NamingIntegrating ADS with Existing DNS Structure Domain name and sites. Active Directory domain name Migration to Windows 2000 DNS DNSDeploying DNS to Support Active Directory Partitioning, and Replication Choosing your ZonesUsing Automatic Configuration Wins ReferralIxfr For More Information IxfrWindows 2000 White Paper