bind configfiles (Was: Re: policy violation and bug reports.)
Manoj Srivastava <srivasta@datasync.com> writes:
> Mark> Unforunately bind doesn't distinguish between zone files it is
> Mark> authoritative for which could and IMO should go in /etc, and
> Mark> those it secondaries which need to be in /var;
>
> I do not understand. Do secondaries get to be huge? or they are not
> user modifiable?
>
> Mark> you have to specify one path for all of them, so really the
> Mark> users' authoritative zone files have to go in /var, and although
> Mark> we could put symlinks in for named.local and named.rev-local, do
> Mark> we want to when none of the zone files will be like that?
>
> I'm not sure I understood the last sentence, but yes, I think
> we need to put any user modified files in /etc/named, and symlink
> back to /var/named if needed.
>
> This is not a problem, is it?
If it gets big, it is. Putting zonefiles in /etc doesn't scale very
well, as you need a _big_ root partition. At my workplace we have
about 6000 primary zone files, some of them quite huge, and a somewhat
smaller number of secondary sone files.
named.local and named.rev-local are (IMHO) part of bind's database,
even if people enter data in them manually and directly. Altering
them changes the answers bind gives, but not the way bind operates.
--
SSM - Stig Sandbeck Mathisen
Trust the Computer, the Computer is your Friend
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: