Displaying 2 results from an estimated 2 matches for "named_run_chrooted".
2020 May 15
2
Samba and DNS backend question
I had configured Samba AD's with Bind9_DLZ in all DC. But for some reason
(i couldn't determine) three (sambadc02,03,04) AD's responded very slowly
. So change to Samba_Internal backend into the servers with problem and
works fine.
sambadc01 -> with FSMO roles - Bind9_DLZ
sambadc02 -> Samba_Internal
sambadc03 -> Samba_Internal
sambadc04 -> Samba_Internal
My question is:
2020 May 15
3
Samba and DNS backend question
Hi Rowland,
1. Thanks for you clarification ;)
2. About, my old DLZ configuration is:
Versions: bind-9.11 - S.O Centos 7.8
This was the sambadc04 with the old bind dlz backend .
[..........]
[root at sambadc04 ~]# cat /etc/sysconfig/named |grep -v '^#'
NAMED_RUN_CHROOTED="no"
OPTIONS="-4"
[..........]
The /etc/named.conf
[..........]
acl "trusted" {
192.168.0.0/16;
10.0.0.0/8;
localhost;
};
options {
listen-on port 53 { any; };
//listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/d...