Planning A Dns Strategy - Novell NETWARE 6-DOCUMENTATION Manual

Planning a DNS Strategy

58
Novell DNS/DHCP Management Utility Administration Guide
Plan to create an Organizational Unit (OU) container object near the top of
your eDirectory tree. The location of this container object should be easily and
widely accessible. Locate the DNS/DHCP Group and Locator objects and the
RootServerInfo Zone object under the container object.
Plan to create an Administrator Group object under this container also. An
administrator group should have Read and Write rights to all DNS/DHCP
Locator object attributes except the global data and options fields. Members
of this group can use the DNS/DHCP Management Utility to create and
modify DNS and DHCP objects.
IMPORTANT:
A network administrator can access only his or her administrative
domain which might not include the DNS/DHCP Locator object. By creating an
administrative group, you enable administrators who are group members to use the
DNS/DHCP Management Utility.
Plan to locate your DNS and DHCP servers at locations where they are
geographically close to the hosts that require their services. Plan to have one
DHCP server in each partition of your network to minimize any WAN
communications problems caused by normal load, configuration changes, or
replication.
Replicate the partition containing the DNS/DHCP Group and Locator objects
to all parts of the network that use DNS/DHCP services to ensure access in the
event of system unavailability or hardware problems.
When planning your DNS replication strategy, consider that replication is
employed for load balancing when you provide multiple name servers within
the DNS zone.
Well-planned replication is the best way to provide fault tolerance for DNS/
DHCP services.
Plan to install and operate a primary name server and at least one secondary
name server. Secondary name servers provide load balancing and robustness
to your DNS implementation.
When you configure your zone, the primary name server is considered
authoritative for the zone, meaning that it contains the most up-to-date
information about the zone and all the hosts within it.
A secondary name server receives its zone data from the primary name server.
When it starts up and at periodic intervals, the secondary name server queries