Questions on bind-chroot

Is it necessary for named.conf in the chroot path and /etc path to be same [root@denver named]# ls -ltrh /etc/named.conf -rw-r-. 1 root named 904 Jun 6 14:50 /etc/named.conf [root@denver named]# ls -ltrh /var/named/chroot/etc/named.conf -rwxr-xr-x. 1 root root 1.1K Jun 10 18:19 /var/named/ch

RE: Does BIND-9.9.9-P1 change the control command log to not show the zone name?

Ok, thanks. Got it. Thanks, Tuan Vo -Original Message- From: Mark Andrews [mailto:ma...@isc.org] Sent: Monday, June 13, 2016 6:36 AM To: Tuan Vo Cc: bind-us...@isc.org Subject: Re: Does BIND-9.9.9-P1 change the control command log to not show the zone name? It is a unintentional side

Re: Does BIND-9.9.9-P1 change the control command log to not show the zone name?

It is a unintentional side effect of the change. Changing 'command' to 'cmdline' should fix it. This is from master where there are two instances that need fixing. Only the second hunk should be needed for 9.9.x diff --git a/bin/named/control.c b/bin/named/control.c index 75fc278..d947ebb 1006

Does BIND-9.9.9-P1 change the control command log to not show the zone name?

When running the rndc command, the log doesn't show the zone name. Example: # rndc -c rndc.conf freeze nguoianphu.com # rndc -c rndc.conf thaw nguoianphu.com The zone reload and thaw was successful. The logs: 12-Jun-2016 19:51:06.793 received control channel command 'freeze' 12-Jun-2