Microsoft windows 2000 DNS manual Using Automatic Configuration, Wins Referral

Page 67

GLOSSARY

Using Automatic Configuration

 

The Windows 2000 implementation of DNS offers a DNS Server Configuration

 

wizard, which greatly simplifies the DNS server installation and configuration

 

process. For example, it offers an elegant way of priming the root hints for a new

 

DNS server.

 

The Server Configuration Wizard sends to the computer’s preferred and (possibly

 

alternative) DNS server(s) a NS query for the root, ".", node. The response is placed

 

into the root hints of this new server. If no root servers are detected, then the wizard

 

sends the same query to the DNS servers specified in the cache.dns file,

 

corresponding to the root servers on the Internet. If again no root servers are

 

detected, the wizard prompts the user to either make the server a root server (by

 

simply choosing the appropriate option) or manually specify root hints.

 

WINS Referral

 

WINS filled the role of domain and machine locator service for previous versions of

 

Windows NT. Windows 2000 will not require WINS in a NetBIOS-less environment.

 

However, WINS will always be required in a mixed environment where

 

Windows 2000-based machines interoperate with other systems such as

 

Windows NT 4.0, Windows 9X, and Windows for Workgroups.

 

WINS Referral is the recommended way for Windows 2000 DNS clients to address

 

down-level machines registered in WINS. Because Windows 2000 resolvers are

 

optimized to use DNS, they would be much more efficient looking up down-level

 

clients in a DNS database as opposed to WINS database. To enable this kind of

 

lookup, a WINS referral zone can be created in DNS that points to the WINS

 

database.

 

This zone does not perform any registrations or updates; it simply refers DNS

 

lookups to WINS.

 

Whenever Windows 2000-based clients send a query with the unqualified name (for

 

example, ntservermydomain), the default domain name suffix will be tried first.

 

Additional suffixes, however, can be supplied as part of the DHCP configuration. If

 

the name of the WINS Referral zone is one of them, all WINS client names will be

 

able to be resolved.

Windows 2000 White Paper

61

Image 67
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 Replication Model Controlling Access to ZonesZone Type Conversions 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 ManagementWMI Support for DNS Server Administration Administrative ToolsDNS Manager Using Wins and Winsr Records Interoperability IssuesUsing UTF-8 Characters Format Receiving Non-RFC Compliant Data DNS Server PerformanceUtilization 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