The legacy files in /var/named are actually read by bindconfig and used to
generate the named.conf file. I wasn't actually expecting
the named.conf file, being of the bind 4 generation the last time I had to set
up a DNS server and this completely threw me for a
while until by accident I used bindconfig and it automagically modified the
named.conf file, but such is life. If you just configure
by hand you can remove the legacy files AFAIK.
__ _ Debian GNU User
/ /(_)_ __ _ ___ __ Simon Martin
/ / | | '_ \| | | \ \/ / Project Manager
/ /__| | | | | |_| |> < Isys
\____/_|_| |_|\__,_/_/\_\ mailto: [EMAIL PROTECTED]
----- Original Message -----
From: Jonathan Lupa <[EMAIL PROTECTED]>
To: <debian-user@lists.debian.org>
Sent: 14 September 1999 05:01
Subject: simple bind question
> I'm in the process of moving my masq. firewall over to Debian
> and leaving Slackware altogether, but I'm running into a "difference"
> in the bind setup and I am curious about ramifications that I may
> not forsee...
>
> In my old named setup, (I think it was bind 8.1.2) I had a named.conf
> which specified zones, each one with a zone file.
>
> In the debian version (files generated by bindsetup or some such), it
> has the named.conf file, but then uses these /var/named/boot.zones,
> /var/named/boot.options, and a named.boot file, all of which I
> suspect are leftovers from bind 4.
>
> They don't have a man entry, the filenames don't show up in a grep of
> /usr/doc/named/*, and being a lazy man, I figured Id go strait to
> the list.
>
> Now, my first impulse is to just delete them and setup my zonefiles
> as I know how. The million dollar question is : In what way is this
> going to hose me when I need to update bind (assuming they ever fix
> the licence. (: )....
>
> Thanks!!
>
> --
> Jonathan Lupa
> [EMAIL PROTECTED]
>
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
>
