How to Manage DNS Zone
Enterprises normally partitions DNS NameSpace into zones called dns zones. Each DNS zone is intended for specific purpose. For example, A DNS zone for Mail Server and other zone for Data base Servers and so on.
However, having multiple DNS zones each having different network traffic, it's essential to manage network bandwidth across the zones.
The following illustrates methods to manage dns zones for windows 2003 and windows 2008:
1. First, Review the traffic patterns in the network.
If each kind of traffic pattern, create a zone. ex .mail.mydns.com 2. Second, Review internal broadcast traffic between DNS servers.
If DNS server is used on router or in router network, then try to avoid DNS server to be used on router
3. Verify the communication traffic between DNS zone servers.
DNS Server to DNS server traffic happens when dns zone transfer happens with other DNS zone servers, DNS interoperability with other servers like Internet Name Service (WINS).
4. Verfiy the DNS Client-to-DNS zone server traffic
DNS queries and dynamic DNS zone updates are sent from DNS clients or DHCP servers on behalf of DNS clients.
5. Finally, study, test, analyze, and revise managing dns zone plans based on observed or estimated traffic patterns.
It's easy for small and flat DNS namespaces to use full replication of a DNS zone files to all DNS servers. However, For large and vertical namespaces, it is often necessary to study, test, analyze, and revise your zone plans based on observed or estimated traffic patterns. After careful analysis, you can partition and delegate your DNS zones based on requirements to provide efficient and fault-tolerant name service to each location or site.
6. Use incremental zone transfers between DNS zone servers to replicate the standard DNS zone files.
7. Use caching-only servers that do not host DNS server zones
Caching-only servers are a good option at small remote sites that have a stable and minimal use for DNS name service.
8. Optimize forward and reverse DNS zone lookups.
Cache the dns zone lookups for subnet or intranet host names.
9. Use authoritative dns zone servers wherever possible.
10. last but not lease always try to integrate DNS zones with Active Directory Domain Services (AD DS).
However, having multiple DNS zones each having different network traffic, it's essential to manage network bandwidth across the zones.
The following illustrates methods to manage dns zones for windows 2003 and windows 2008:
1. First, Review the traffic patterns in the network.
If each kind of traffic pattern, create a zone. ex .mail.mydns.com 2. Second, Review internal broadcast traffic between DNS servers.
If DNS server is used on router or in router network, then try to avoid DNS server to be used on router
3. Verify the communication traffic between DNS zone servers.
DNS Server to DNS server traffic happens when dns zone transfer happens with other DNS zone servers, DNS interoperability with other servers like Internet Name Service (WINS).
4. Verfiy the DNS Client-to-DNS zone server traffic
DNS queries and dynamic DNS zone updates are sent from DNS clients or DHCP servers on behalf of DNS clients.
5. Finally, study, test, analyze, and revise managing dns zone plans based on observed or estimated traffic patterns.
It's easy for small and flat DNS namespaces to use full replication of a DNS zone files to all DNS servers. However, For large and vertical namespaces, it is often necessary to study, test, analyze, and revise your zone plans based on observed or estimated traffic patterns. After careful analysis, you can partition and delegate your DNS zones based on requirements to provide efficient and fault-tolerant name service to each location or site.
6. Use incremental zone transfers between DNS zone servers to replicate the standard DNS zone files.
7. Use caching-only servers that do not host DNS server zones
Caching-only servers are a good option at small remote sites that have a stable and minimal use for DNS name service.
8. Optimize forward and reverse DNS zone lookups.
Cache the dns zone lookups for subnet or intranet host names.
9. Use authoritative dns zone servers wherever possible.
10. last but not lease always try to integrate DNS zones with Active Directory Domain Services (AD DS).
0 comments:
Post a Comment