Re: multiple slave zones pointing to same file?
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
Re: multiple slave zones pointing to same file?
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. Thanks Gordon...I didn't think about the origin issues until I opened up one of the secondary zone files and saw that! ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: multiple slave zones pointing to same file?
Simply set the file option to the same name on the slave server.
On 10/2/2010 2:59 PM, Doug Barton wrote:
On 10/2/2010 11:16 AM, online-reg wrote:
Hi All: I’m building a new Bind 9.7.1-P2 slave server and am taking an
opportunity to review my conf files.
I have a number of zones on the primary that all point to the same zone
configuration file. On my slave server, is there any way to configure
named.conf so that multiple zones are all “aliased” to the same zone
config?
Previously, I was using a basic slave config statement for each zone:
zone domain.com { type slave; file domain.com.zone; masters {
192.168.0.1; }; };
but, it seems like a lot of unnecessary files are being created?
I thought about using the same file name for all the slave zones
statements in named.conf, but wouldn't that force the file to be
overwritten multiple times for no reason?
How often does the file change? If the answer is not often then a
little file system churn is harmless.
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.
hth,
Doug
___
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
Re: multiple slave zones pointing to same file?
In message 58f2f2eb90f24743a050575c87c7c...@nyoffice.enigmedia.local, online -reg writes: Hi All: Iâm building a new Bind 9.7.1-P2 slave server and am taking an opportunity to review my conf files. I have a number of zones on the primary that all point to the same zone configuration file. On my slave server, is there any way to configure named.conf so that multiple zones are all âaliasedâ to the same zone config? No. Named does NOT support this. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: multiple slave zones pointing to same file?
Doesn't support it? Since when does named not allow you to use the same file name for more then one zone? I've been doing that for several years. -- John Wingenbach On 10/2/2010 6:49 PM, Mark Andrews wrote: In message58f2f2eb90f24743a050575c87c7c...@nyoffice.enigmedia.local, online -reg writes: Hi All: IâEUR^(TM)m building a new Bind 9.7.1-P2 slave server and am taking an opportunity to review my conf files. I have a number of zones on the primary that all point to the same zone configuration file. On my slave server, is there any way to configure named.conf so that multiple zones are all âEURoealiasedâEUR? to the same zone config? No. Named does NOT support this. Mark ___ 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
Re: multiple slave zones pointing to same file?
In message 4ca7b926.9070...@wingenbach.org, John Wingenbach writes: Doesn't support it? Correct. It is not supported. Don't take the fact that it doesn't complain as evidence that this is supported practice. The only place where shared file use is supported is in static master zones. Since when does named not allow you to use the same file name for more then one zone? I've been doing that for several years. You should not use the same file name for any zone named writes. This includes slave and stub zones, master files that named updates. Doing so will cause problems. Some of this named will detect on restart and correct by re-transfering the zone. Others it can't and those require manual intervention. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: multiple slave zones pointing to same file?
On 10/2/2010 3:15 PM, online-reg wrote: 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 is expensive. hth, Doug -- Breadth of IT experience, and| Nothin' ever doesn't change, depth of knowledge in the DNS. | but nothin' changes much. Yours for the right price. :) | -- OK Go http://SupersetSolutions.com/ ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
