On Tue, 21 Dec 2004, Stephane Bortzmeyer wrote:
On Mon, Dec 20, 2004 at 04:52:07PM -0500,
Stuart D. Gathman <stuart(_at_)bmsi(_dot_)com> wrote
a message of 30 lines which said:
However, the BIND DNS server does not help much with that situation.
It does. The trick I use when I have to manage hundreds of identical
zone files (something which is common for an ISP which hosts the DNS,
mail and Web for its clients) is to have *one* zone file, managed by
hand, and then to have symbolic links to it:
-rw-r--r-- 1 foobar foobar 365 Nov 08 10:52 example.com
lrwxrwxrwx 1 foobar foobar 11 Apr 20 10:07 example.net -> example.com
lrwxrwxrwx 1 foobar foobar 11 Apr 20 10:07 example.org -> example.com
Why bother? Youn can simply point to the same file for different zones
inside the named.conf:
zone "completewhois.com" IN {
type master;
file "domains/completewhois.com.zone";
allow-update { none; };
};
zone "completewhois.net" IN {
type master;
file "domains/completewhois.com.zone";
allow-update { none; };
};
The only trap is to be sure to use only *relative* names in the zone
file (such as @). For instance, here is a typical zone file which do
not include absolute names and therefore is suitable for the symbolic
link trick.
Yes.
--
William Leibzon
Elan Networks
william(_at_)elan(_dot_)net