BIND logs when run in a chroot

[Hova]

Hello.

First of all wanted to clarify that this post is not a problem if a query.

Well, I wanted to ask about BIND9 logs when running within a chroot.

I have configured a BIND9 in a chroot successfully and within the rsyslog configuration add the line:

$ AddUnixListenSocket "chroot path"/dev/log

This line is used to create a socket rsyslog on /var/log/messages so you can write log messages, and otherwise to be within the chroot can not.

Now my question is this. I have no very clear as BIND9 know you have to send log messages to this socket, because i never define it in the named.conf but also the messages appear in /var/log/messages.

Well if you need more info. or do not understand my question let me know.

Many thanks.

[Lazydog]

I am not sure what you are looking for but I wouldn't worry about having bind write to the message file as bind can write to it's own log file by configuring the logging in named.conf file.

[Hova]

Yes. I know the loggin feature of BIND. Is how to use it.

I also know that the rsyslog has the function of creating a socket to use it within the chroot.

My question was, how it is that BIND uses this function of rsyslog when running inside a chroot.

Thank you very much.