Microsoft windows 2000 DNS manual Server Capacity Planning, Hardware components Sizing

Page 51

Hardware components

Sizing

Number of processors

Two

Processor

Intel Pentium II 400 MHz

Amount of RAM

256 MB (megabytes)

Hard disk drive space

4 GB (gigabytes)

These measurements were based on the server computer running a DNS server and with no other services in use. Where other hardware specifications or software configurations are used when deploying Windows 2000 DNS servers, your performance results are likely to vary from those documented here.

Server Capacity Planning

Planning and deploying DNS servers involves examining several aspects of the network and the capacity requirements for any DNS servers that will be used.

In many cases, adding more RAM to a DNS server can provide the most noticeable improvements in performance. This is because the DNS Server service fully loads all its configured zones into memory at startup. If the server is operating and loading a large number of zones, and dynamic updates are occurring frequently for zone clients, additional memory can be helpful.

The DNS server consumes memory as follows:

Approximately 4 MB of RAM is used when the DNS server is started without any zones.

For each addition of zones or resource records to the server, the DNS server consumes additional server memory. Its estimated that for the addition of every resource record to a server zone, an average of approximately 100 bytes of server memory is used.

For example, if a zone containing 1000 resource records is added to a server, it would consume approximately 100 KB (kilobytes) of server memory. he previous recommendations are not meant in any way to indicate maximum performance or limitations for Windows 2000 DNS servers.

Note: These numbers are approximate and can be influenced by the type of the resource records entered in zones, the number of resource records with the same owner name, and the number of zones in use at a specific DNS server.

Before a DNS namespace can be properly implemented in Windows 2000, the Active Directory services structure needs to be available. The recommended approach to the ADS and DNS design is to begin with the ADS design and then support it with the appropriate DNS namespace.

Active Directory design is an iterative process. It involves developing an initial ADS

Windows 2000 White Paper

45

Image 51
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 Controlling Access to Zones Replication ModelZone 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 ManagementAdministrative 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