On Saturday 10 March 2007 23:07, M Harris wrote:
> ... the client only moves to the second nameserver if the first is
> unavailable...
And the other thing I'm gonna have to experiment with now are the
"forwarders" in named.conf. If the the local dns does not resolve the name
then it forwards the resolution request to the "forwarders" listed in
named.conf file. And I thought if the first does not resolve the name, then
the second would pick it up... but probably not... if the first is available
and does not resolve the name then the name remains unresolved??
I suppose the way to handle this is to make the first server a caching
nameserver forwarding to the second server and then outside. The second
server then forwards only outside. Changes are made to the second server
*only* (or it caches from outside) and the primary server gets its changes by
caching the second. If the primary is down the secondary gets it. If the
secondary is down the primary forwards to its secondary forwarder (outside).
I'm gonna have to play with this some more.... just for fun... :)
--
Kind regards,
M Harris <><
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
