bind configs over NFS - problem with transfer-source
Kevin Darcy
kcd at daimlerchrysler.com
Wed Sep 8 22:27:20 UTC 2004
Pete Ehlke wrote:
>On Wed Sep 08, 2004 at 14:05:38 -0700, Dale wrote:
>
>
>>I've been sharing named.conf files over nfs for a couple years now on
>>bind9 and it's been working just fine. The problem I'm having now is
>>that in doing a zone transfer, bind uses the IP bound to eth0 instead
>>of the (an) IP in listen-on{}.
>>
>>listen-on{} accepts as many IPs as you can throw at it, and bind just
>>skips the address if it's not bound to the NIC. I need to use
>>transfer-source now (bind is bound to eth0:0), and I can't think of a
>>workaround that would allow me to keep sharing my bind configs while
>>getting transfer-source to be unique on each system that shares the
>>files.
>>
>>Does anyone have any suggestions on how I can do this? I'm really not
>>interested in changing the layout of the nfs configs at the moment, so
>>a good workaround or another option would be nice.
>>
>>
>>
>Kill the nfs scheme. rsync is your friend.
>
But that just changes the way that configs are propagated. It doesn't
solve the issue of needing to have unique configs on each box.
Personally, I just use "include" files for things that are specific to a
particular box.
- Kevin
More information about the bind-users
mailing list