Microsoft windows 2000 DNS manual Ldap.tcp.dc.msdcs.DnsDomainName

Page 38

_ldap._tcp.<SiteName>._sites.<DnsDomainName>.

Allows a client to find an LDAP server in the domain named by <DnsDomainName> and is in the site named by <SiteName>. For example, _ldap._tcp.redmond._sites.nt.microsoft.com. All Windows NT Domain controllers will register this name.

_ldap._tcp.dc._msdcs.<DnsDomainName>

Allows a client to find a DC of the domain named by <DnsDomainName>. All Windows NT Domain controllers will register this name.

_ldap._tcp.<SiteName>._sites.dc._msdcs.<DnsDomainName>

Allows a client to find a DC of the domain named by <DnsDomainName> and is in the site named by <SiteName>. All Windows NT Domain controllers will register this name.

_ldap._tcp.pdc._msdcs.<DnsDomainName>.

Allows a client to find the primary DC (PDC) of the domain named by <DnsDomainName>. Only the PDC of the domain registers this name. The PDC is responsible for deregistering any other registrations of this name.

_ldap._tcp.gc._msdcs.<DnsForestName>.

Allows a client to find a Global Catalog (GC) server for this domain. Only a DC serving the GC of the forest named by <DnsForestName> registers this name. For example, _ldap._tcp.gc._msdcs.microsoft.com.

_ldap._tcp.<SiteName>._sites.gc._msdcs.<DnsForestName>.

Allows a client to find a Global Catalog (GC) server for this domain and is in the site named by <SiteName>. Only a DC serving the GC of the forest named by <DnsForestName> registers this name. For example, _ldap._tcp.redmond._sites.gc._msdcs.microsoft.com.

_gc._tcp.<DnsForestName>.

Allows a client to find a Global Catalog (GC) server for this domain. Only an LDAP server serving the GC of the forest named by <DnsForestName> registers this name. For example, _gc._tcp.microsoft.com. The LDAP server is not necessarily a DC.

_gc._tcp.<SiteName>._sites.<DnsForestName>.

Allows a client to find a Global Catalog (GC) server for this domain and is in the site named by <SiteName>. Only an LDAP server serving the GC of the forest named by <DnsForestName> registers this name. For example, _gc._tcp.redmond._sites.microsoft.com. The LDAP server is not necessarily a DC.

_ldap._tcp.<DomainGuid>.domains._msdcs.<DnsForestName>. Allows a client to find a DC in a domain with a GUID of <DomainGuid>. This operation will only be done if the <DnsDomainName> of the domain has changed and the <DnsForestName> is known. This operation is expected to be infrequent. This operation will only function if the Dns Forest Name has not also been renamed. For example, _ldap._tcp.4f904480-7c78-11cf-b057- 00aa006b4f8f.domains._msdcs.microsoft.com. All Windows NT Domain controllers will register this name.

_kerberos._tcp.<DnsDomainName>

Allows a client to locate a Kerberos Key Distribution Center (KDC) for the domain.

Windows 2000 White Paper

32

Page 37 Page 39
Image 38
Page 37 Page 39
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 NamesMit Mydomain Int/net/orgCom Edu Gov Mil Army Microsoft 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 DescriptionMaster DNS Server Dynamic UpdateZone Log File Slave DNS Server Ixfr and DS IntegrationUpdate Algorithm Dynamic Update of DNS RecordsMixed Environment Dhcp ClientRAS Client Statically Configured ClientSecure Dynamic Update 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 ScenariosDNS Server List Management Fully-Qualified Query ScenariosMicrosoft Implementation of Negative Caching 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
Top Page Image Contents