About Secondary NS

[Kevin Darcy]

Either the slave responds or it doesn't. There is no "check the availability/reachability of the master and only answer the query if the master is down" mechanism within
BIND's nameserver. You have to somehow *tell* the slave when to respond and when not to respond. In that case, why bother even running a nameserver on the slave at all when
the master is up? Why not just have your "master down" detection mechanism -- whatever that its -- start up the slave's nameserver anew?

What is it that you are really trying to achieve here? Fast visibility of changes? NOTIFY should take care of that. If NOTIFY is not fast enough for you, then you can always
follow Dan Bernstein's suggestion and have both servers defined as "master" with some sort of fast, secure, out-of-band mechanism -- Dan recommends rsync-over-ssh -- do the
replication from the real master to the real slave(s). Note also that your TTL settings probably have a lot more to do with how fast changes become visible to the world, than
the speed/frequency of replication between your master and its slaves.

                                                                                                                                                        - Kevin

Sumit Mehrotra wrote:

> Is there a way to to stop secondaries from responding, so that all request are handled by the master? The secondary should , however , be up, incase the primary goes down.
>
> Thanks
> - Sumit
>
> > Yes, secondaries will answer all queries for which they have
> > information. The primary server(s) has/have no influence on the response
> > that the secondary gives in this respect.
> >
> > Geert-Jan
> >
> >
> >