RE: [opensuse] setting up secondary DNS with Yast (SuSE 10.0)
On Thursday 08 March 2007 17:01, James D. Parra wrote:
Is there a way in Yast, when configuring it as a DNS server, to have it go and retrieve the named info from the primary DNS server or must I load that info manually? Not in Yast.
Clone the config by manually copying the zone information on the one machine from /var/lib/named/ to the other machine. You can specify the order of the primary and backup nameservers in your dhcp server by setting the config line in /etc/dhcpd.conf option domain-name-servers 192.168.1.3, 192.168.1.5; The named zone info is identical between the two servers, and the .1.3 server (in this case) will be the primary... assuming that your dhcp clients are setup to pull the nameserver addresses ( resolv.conf ) from dhcp. ~~~ Thank you for your help. Is there a way for the second DNS server to poll info from the first DNS server? For example, if a change is made on the primary server the Secondary server polls the first and adds the change to its own name list. I have seen this on other DNS servers products and I was hoping that Bind might be able to accomplish the same thing. Best regards, ~James -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Is there a way for the second DNS server to poll info from the first DNS server? Sure, but there is no need really... when searching for name resolution the client searches the nameservers in order... if not finding a resolution on
On Friday 09 March 2007 08:05, James D. Parra wrote: the first, it moves to the second and so on---- even moving off-site if you have so configured it. -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 09 March 2007, M Harris wrote:
Is there a way for the second DNS server to poll info from the first DNS server? Sure, but there is no need really... when searching for name resolution the client searches the nameservers in order... if not finding a resolution on
On Friday 09 March 2007 08:05, James D. Parra wrote: the first, it moves to the second and so on---- even moving off-site if you have so configured it.
I don't believe that is true. Clients only use the second dns server if the first becomes unreachable. -- _____________________________________ John Andersen
On Friday 09 March 2007 23:44, John Andersen wrote:
I don't believe that is true. Clients only use the second dns server if the first becomes unreachable. yikes...
... well I'm gonna have to experiment with this a bit... would not be the first time I thought I understood something only to find out I still needed to understand it... :-)) stand by... -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 10 March 2007 22:34, M Harris wrote:
yikes...
... well I'm gonna have to experiment with this a bit... would not be the first time I thought I understood something only to find out I still needed to understand it... :-)) stand by... Andersen is correct...
... the client only moves to the second nameserver if the first is unavailable... if the first cannot resolve the name ( but was available to do the lookup ) then the name remains unresolved. rats. So, we're back to the first place... the servers must be identical clones... so that /var/lib/named looks the same for both servers... the zone information is identical between the two. -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
... 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
On Saturday 10 March 2007 23:07, M Harris wrote: 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: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
M Harris wrote:
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... :)
I missed what you need this for, but if the idea is to provide local DNS for a LAN, while also being able to resolve outside names, you may want to look at the "dnsmasq" package. It's designed to do specifically that, and it's easier to set up than a full-blown nameserver. Of course, if your goal is to learn bind, you should go ahead and work on setting up named.conf to do what you want. :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 10 March 2007, M Harris wrote:
... the client only moves to the second nameserver if the first is unavailable... if the first cannot resolve the name ( but was available to do the lookup ) then the name remains unresolved.
This is true for the client side. However I am not sure this is the case for bind itself. It might be smart enough to check all its sources / referrers (or what ever its upstream is called). -- _____________________________________ John Andersen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
David Brodbeck -
James D. Parra -
John Andersen -
M Harris