The slave files do not carry the "@" I presume you are using on
the master -- the zone-transfer data includes the specific domain
names -- so the slave files can't be shared even if they could be
shared.

Maybe you can write a program that translates the slave data
into the sharable format, and every time there is a zone transfer,
you can run the program to generate a sharable file, and then
have all the rest of your zone set up as masters, and have
your program do an rndc reload after generatign the shared
file....   ;-)

or just use separate files.

--
Gordon Lang

----- Original Message ----- From: "online-reg" <online-...@enigmedia.com>
To: <bind-users@lists.isc.org>
Sent: Sunday, October 03, 2010 9:47 AM
Subject: Re: multiple slave zones pointing to same file?


IME the best way to do this on a Unix'y system is to use hard links.
That way if you ever need to change one of them to be its own file
it's trivial to do so. Also IME, BIND doesn't react well to having
multiple slave zones sharing the same file, but that may have improved
in more recent versions, I haven't tried it for a couple of years now.

Thanks Doug, but I'm not entirely clear on what you're recommending? It
seems like you're saying it's OK, but then you're saying BIND doesn't
like it?

I'm guessing then that you're not running BIND on a Unix system. In any case, Mark is in a much better position than I to state categorically, "Don't do that" so I am happy to defer to his wisdom.

Just use different files for each zone. Yes, it's a bit of duplication on the file system, but that's not the end of the world. Disk is cheap, DNS failure i

Thanks Doug/Mark...I ended up just doing it the "right" way ;)


_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Reply via email to