Академический Документы
Профессиональный Документы
Культура Документы
Recursive and Iterative Queries Name Caching Forwarders Root Hints Delegation and Glue Records
Recursive Query
DNS Client querying for: Mail1.Contoso.Com Recursive Query to its Configured DNS Server 1. Client sends recursive query to local DNS Server
2. Local DNS Server checks: Forward lookup zone Cache 3. If found, the DNS Server
server.
2. Process continues until Local DNS receives Authoritative
Response
3. Response is then sent to the DNS client
Referral
The DNS Server caches Host Name and IP Address of: Host Names resolved via iterative queries to other DNS Servers
DNS Server uses its cached data in conjunction with its zone data to resolve subsequent queries: If specific Host/IP Mapping are in cache Server returns that data to querying host
Will used cached Name Server data when trying to resolve subsequent queries to unknown domains
Negative Caching
If DNS Server learns that Host Name is invalid or does not exist from an authoritative server, it caches that information
On subsequent queries it can then respond to client without attempting to contact the remote Server
DNS Client (Resolver) also caches resolved Host Name/IP Mapping data Client checks local cache before contacting DNS Server Local HOSTS file, if it exists, is pre-loaded into cache at startup Clients also perform Negative Caching Entries remain in cache for duration specific by TTL
ADVANTAGE PRO ADVANTAGE PRO Chennais Premier Networking Training Center
Forwarders
If DNS Server cannot resolve name using local or cached data, it must communicate with other name servers to resolve request, often across Internet or WAN
Forwarders are DNS Servers configured to handle queries that cannot be resolved using local data, and for which queries across the Internet or WAN are necessary
Reduces workload on local DNS Servers, tasks specific machines with remote query functions
Forwarder Behavior
DNS Servers may be configured with address of one or more Forwarders DNS Servers use Forwarders in one of two modes Non-exclusive mode
DNS Server passes queries that cannot be resolved with local data to specified Forwarder If Forwarder cannot resolve request, local DNS Server attempts resolution via normal process of iterative queries via Root Hints.
Exclusive Mode
Same as above, except local Server does not attempt resolution via Root Hints if Forwarder cannot resolve request.
Windows 2003 DNS Servers can be set Exclusive via Do not use recursion option in Server properties.
Root Hints
Configuration
DNS Servers configured to only query and cache Not authoritative for any domain No zone files only cached data Windows 2003 DNS Servers function as Caching Only servers at initial install if no zones are configured
Summary
Recursive and Iterative Queries Name Caching Forwarders Root Hints Delegation and Glue Records
Discussion Topics
Name Server Types Zone Transfer Process Active Directory Integration of DNS Zones Round Robin Subnet Prioritization
DNS Servers can be configured with several zone types or none at all:
Normal Operation
Standard Primary Standard Secondary AD Integrated
Numerous options for optimal configuration based on network topology, size of namespace, etc.
Zone Types
Standard Primary Zone Authoritative server for its zone (or zones) Hosts master (writeable) copy of zone file(s) Changes to Zone Data are carried out on this servers local zone files In Win2k, supports dynamic update of zone files Standard Secondary Zone Receives its Zone Data and updates from authoritative Master Name server in its zone via Zone Transfer process
Master Server Server from which a Secondary Name Server receives its zone data and updates NOTE: A Secondary can function as Master to another Secondary
Zone Data is stored in Active Directory database Only on Windows 2003 Domain Controllers Multiple writable / master copies of zone
Caching-only Servers
ADVANTAGE PRO ADVANTAGE PRO Chennais Premier Networking Training Center
Zone Types
Transfer of Records to a Secondary Name Server in a Zone Pulled from a Master Server
DNS Notify
Notification of Change
Notification Process:
Serial Number field in the SOA RR is updated Master sends a Notify message to servers on the Notify List Secondary servers initiate the Zone transfer process
Secondary polls the master server for its SOA RR Secondary compares master SOA serial number to its own If the number from the master is higher The zone database on the secondary is out of date Full Transfer (AXFR) query is sent to the master Master responds with the full zone database
ADVANTAGE PRO ADVANTAGE PRO Chennais Premier Networking Training Center
The Retry field specifies how often the secondary retries the process
Incremental Transfer
Based on Zone Version History
Secondary sends an Incremental Transfer (IXFR) instead of AXFR query Master sends only changes unknown to the secondary
AD Integrated Zone
Benefits:
Fault Tolerance Security Simplified Management More Efficient Replication of Large Zones
MultiMulti-master Replication
DNS Transfers
Full Zone Transfers send the Entire Database Incremental Zone Transfers send Each Change
Per-Property Processing
SOA Records
Replication Collision
Round Robin
Multiple Resource Records for one name (same name, different IP Addresses) Server rotates order of A records when responding Example with three A records:
1. Third client receives the address 172.18.64.33 2. The next client would receive the first address in order as the
Enabled by Advanced Properties of the DNS Server setting in the DNS MMC
Response is reordered based on the subnet of the client and resource record (RR) The host Srv1.newcorp.com has three host IP addresses registered in DNS zone data DNS Client queries the DNS Server to resolve Srv1.newcorp.com The DNS Server notes the originating IP of the client, and reorders the response to provide address matching clients own network List is not prioritized if no local network match is found
Summary
Name Server Types Zone Transfer Process Active Directory Integration of DNS Zones Round Robin Subnet Prioritization