[ Thanks to Falko
Timme for this link. ]
“In our scenario, we need each master and slave
server(s) as both “authoritative” and
“caching”. So it is very important to understand that
how to achieve these with djbdns. Unlike bind, djbdns uses
individual IP for each kind of dns service. By default each system
is ready with 2 IP’s => one host-IP and other is loopback-IP. So
any system on LAN should hit caching dns, hence the host-IP for
caching-dns. And we will run authoritative on loopback-IP, and
later bind that to caching-dns, hence LAN hosts can query
authoritative host records also.”