Configuring A Dns Server To Forward Requests; Forwarding Requests For Unknown Addresses - Novell NETWARE 6-DOCUMENTATION Manual

Configuring a DNS Server to Forward Requests

Forwarding Requests for Unknown Addresses

60
Novell DNS/DHCP Management Utility Administration Guide
You are using a master DNS server and do not want to designate it as a
primary name server because of the responsibility it entails.
This approach is easy to implement in your existing DNS model.
You want to install more secondary name servers to provide better load
balancing.
You want to gradually make the transition to operating a primary name
server.
If a name server cannot answer a query, it must query a remote server. You can
configure primary or secondary name servers to act as forwarders. When you
designate a server to be a forwarder, all off-site queries are first sent to the
forwarder.
Forwarders that handle the off-site queries develop a robust cache of
information. The forwarder probably can answer any given query with
information from its cache, eliminating the need to make an outside query to
a remote server.
When you decide to make a server a forwarder, configure the other servers in
your zone to direct their queries through the forwarder. When a forwarder
receives a query, it checks its cache for the information. If the information is
unavailable, the forwarder issues a query to the root server.
For more information, refer to:
"Forwarding Requests for Unknown Addresses" on page 60
"Restricting Forwarding" on page 61
When you configure your name servers, you provide information about where
to forward requests that the servers cannot answer. If you are configuring to
use forwarders, you provide the names and IP addresses of servers above your
location in your domain. Configure your other name servers to issue queries
to the forwarders for queries they cannot answer.
Even if you are using forwarders, a name server that does not receive a timely
response from its forwarder eventually attempts to query a root server directly.