Microsoft windows 2000 DNS manual Ixfr

Page 68

Windows NT 4.0- and Windows 2000-based clients register in WINS

NTDEV.MICROSOFT.COM

Windows 2000-based clients register in DNS

WINS Server

WINS.NTDEV.MICROSOFT.COM

WINS Referral

Windows 2000

-based client

Windows 2000

-based client

Windows NT	Windows NT	Windows NT	Windows 2000
4.0-based client	4.0-based client	4.0-based client	-based client

In the picture above, a WINS referral zone called wins.mydomain.microsoft.com. has been created and pointed to the WINS database. Assume that a Windows NT 4.0-based client has a name client1. A Windows 2000-based client belongs to the mydomain.microsoft.com. If the Windows 2000-based client has received a wins.mydomain.microsoft.com. suffix with its DHCP configuration, then in an attempt to resolve an unqualified name client1, it will first try the mydomain.microsoft.com. suffix (that is, client1.mydomain.microsoft.com.), and if that fails, it will then try wins.mydomain.microsoft.com. (that is, client1.wins.mydomain.microsoft.com.). When the DNS server authoritative for the wins.mydomain.microsoft.com. zone receives the query it can’t resolve the requested name. But since it is configured to use WINS look-up it submits a query for client1 to the WINS server. The WINS server containing appropriate registration returns the host IP address to the DNS server and that passes it to the Windows 2000-based client.

Microsoft has chosen DNS to be its strategic name space in Windows 2000 replacing NetBIOS used as a name service in previous versions of Windows NT.

The implementation of DNS in Windows 2000 is a unique DNS Server implementation that is fully interoperable with other standards-based implementations of DNS Server. It is a scalable, highly available, and high performance solution. The following features of Windows 2000 DNS make it a good choice for the corporations looking to implement a reliable hierarchical distributed network environment:

•ADS Integration

•IXFR

•Dynamic Update and Secure Dynamic Update

•Unicode Character Support

•Enhanced Domain Locator

Windows 2000 White Paper

62

Image 68

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