hi stephen,
thanks for your prompt answer.
in the past, bind9 used to log a warning about the named.conf zones
being not in views, while i defined other zone files within views in
named.conf.local, which is included in named.conf.
recently, bind9 was shipping with all the zones in named.conf included
in view "original", probably to overcome that warning.
the "include named.conf.local" statement is outside view "original"
{...};, so my views would, without changing named.conf, be not nested
within view "original".
i have nevertheless changed this to have nested views, as you said, but
the server fails to even load. the only possible way for it to load
would be to have the include statement within view "original", but
refrain from containing view or logging statements in the local file,
which would unnecessarily limit it's functionality.
as an obeying user, i have migrated only named.conf.local from a running
server, but failed to work on a newer system. hence the problem gravity.
my fix preserves the former situation, with the given warning, but lets
the system run properly.
alex
Stephen Gran wrote:
> severity 374093 normal
> kthxbye
> This one time, at band camp, alex bodnaru said:
>
>>the bind9 server failed to serve all zones i have defined, but does work
>>as a dns forwarder.
>>i have fixed this situation by removing the view "original" { }; from
>>named.conf, but keeping it's contents, of course.
>
>
> You'll need to define the zones you want served in a view within that
> view - they do not inherit. I am glad you fixed your problem.
>
> There are no views defined in the Debian package for bind9. I am
> guessing this is a local configuration problem, and nothing to do with
> the packaging. I am downgrading to normal, but I suggest the
> maintainers follow up and close this as appropriate.
>
> Take care,
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
