RE: [cobalt-users] redundancy how too....

[<rpaiz@xxxxxxxxxxxxxx>]

> I thought the secondary name server, based on the ttl of the primary,
> reached out and "asked" the primary "do you have anything for me?"

I know for sure you are correct... if the slave has been configured to
know it's a slave. That is, you tell your server that it will run slave
for domain.com whose master is 111.222.333.444, and at the end of the
expire or refresh period (don't know which), it calls up the master and
says "Has anything changed on domain.com?" The newer BIND packages also
have a NOTIFY feature, where the master will let the slaves know when a
change has been made so that DNS propagates to slaves more quickly.

However, I don't believe this applies to doing slave DNS for an entire
*server*. Then again, the paragraph above is essentially the entire
output of

cat /brain/dns/whatwherehow

so we'll see what corrections get made by other listmembers.

> If the nameservers do talk to each other, it would appear
> that the changes only need be made at the primary.

This is correct, once they've been told to talk to each other.

--
Rodolfo J. Paiz
rpaiz@xxxxxxxxxxxxxx <mailto:rpaiz@xxxxxxxxxxxxxx>