search for: rdnc

...se with command channel 127.0.0.1#953: 1 Time(s) Here's parts of the relevant files: named.conf: controls { inet 127.0.0.1 allow { localhost; } keys { rndckey; }; include "/etc/rndc.key"; <-- does not match above -------------------------------------------------------------- rdnc.conf: options { default-server localhost; default-key "rndckey"; }; server localhost { key "rndckey"; }; key "rndckey" { algorithm hmac-md5; secret "xxxxxxxxxxxxxxxxxxxxx"; }; -------------------------...

Hai Baptiste, You missed my first message but here it is again. . systemctl cat bind9 # /lib/systemd/system/bind9.service [Unit] Description=BIND Domain Name Server Documentation=man:named(8) After=network.target Wants=nss-lookup.target Before=nss-lookup.target [Service] EnvironmentFile=/etc/default/bind9 ExecStart=/usr/sbin/named -f $OPTIONS ExecReload=/usr/sbin/rndc reload

...file (/etc/rndc.conf) rndc: connection to remote host closed This may indicate that * the remote server is using an older version of the command protocol, * this host is not authorized to connect, * the clocks are not synchronized, or * the key is invalid. After a Google search I found: to remove rdnc.key and it was suppose to be working ok. and I chown named:named the file /etc/named.conf, now if I do "service named status" it throws me: version: 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.1 CPUs found: 4 worker threads: 4 number of zones: 17 debug level: 0 xfers running: 0 xfers deferred:...

Am 08.10.2016 um 16:28 schrieb Rowland Penny via samba: > On Sat, 8 Oct 2016 16:13:57 +0200 > Ronny Forberger via samba <samba at lists.samba.org> wrote: > >> Am 08.10.2016 um 16:08 schrieb barış tombul: >>> Have you tried the "smbpasswd administrator" command of? >>> >>> 2016-10-08 16:21 GMT+03:00 Ronny Forberger via samba >>>

Afaik it runs 4.9.15 \- - - mailto:commandline at protonmail.com Joris Lambrecht CyberSecurity and ICT Coach call:?+32 487 558 354 Antwerp,?Belgium https://www.commandline.be \-------- Oorspronkelijk bericht -------- Aan 4 jul. 2020 19:09, Rowland penny via samba < samba at lists.samba.org> schreef: > > > > On 04/07/2020 16:36, commandline at

...ba.org Assunto: Re: [Samba] Problems with bind9_dlz when rndc is reloaded Hi Roger, I'm using Samba as AD DC in version 4.5.0 on Centos 7 with Bind9_DLZ DNS backend, Bind is 9.9.4 and I don't have that issue. I tried reload my bind using systemctl at first and no issue, then I tried "rdnc reload" to be sure rndc was used, still no issue. By no issue I don't mean log are clean, I mean the DNS service is working well (tested using dig commands). In my logs I have the very same complaints about "duplicate zone" which are ignored. In my logs I don't have complai...

Hi Roger, I'm using Samba as AD DC in version 4.5.0 on Centos 7 with Bind9_DLZ DNS backend, Bind is 9.9.4 and I don't have that issue. I tried reload my bind using systemctl at first and no issue, then I tried "rdnc reload" to be sure rndc was used, still no issue. By no issue I don't mean log are clean, I mean the DNS service is working well (tested using dig commands). In my logs I have the very same complaints about "duplicate zone" which are ignored. In my logs I don't have complai...

My BIND9.6.0 on FreeBSD 6.2 works fine when I manually start with: root@ns2# named -4 -S 1024 -c /etc/namedb/named.conf But it won't start on boot and no error messages or log. And it won't start using rndc, it cause error message. Why does the error shows port 953 when I specified for port 53 in the config? rndc: connect failed: 127.0.0.1#953: connection refused Below are

Hi guys, I'm facing a problems with samba4 + bind9_dlz that consuming my time for several days. Everything is working fine until samba4 need to update dns when I'm work with more than one DC server. When samba (or bind) need to reload all zones, the module bind9_dlz is shutting down and then all my environment stops and I need to restart the bind to up again. See my log: ... Jan

...ems with bind9_dlz when rndc is reloaded > > Hi Roger, > > I'm using Samba as AD DC in version 4.5.0 on Centos 7 with Bind9_DLZ DNS > backend, Bind is 9.9.4 and I don't have that issue. > I tried reload my bind using systemctl at first and no issue, then I tried > "rdnc reload" to be sure rndc was used, still no issue. > > By no issue I don't mean log are clean, I mean the DNS service is working > well (tested using dig commands). > > In my logs I have the very same complaints about "duplicate zone" which > are ignored. > In...

...rg> Assunto: Re: [Samba] Problems with bind9_dlz when rndc is reloaded Hi Roger, I'm using Samba as AD DC in version 4.5.0 on Centos 7 with Bind9_DLZ DNS backend, Bind is 9.9.4 and I don't have that issue. I tried reload my bind using systemctl at first and no issue, then I tried "rdnc reload" to be sure rndc was used, still no issue. By no issue I don't mean log are clean, I mean the DNS service is working well (tested using dig commands). In my logs I have the very same complaints about "duplicate zone" which are ignored. In my logs I don't have complai...

...is reloaded >> >> Hi Roger, >> >> I'm using Samba as AD DC in version 4.5.0 on Centos 7 with Bind9_DLZ DNS >> backend, Bind is 9.9.4 and I don't have that issue. >> I tried reload my bind using systemctl at first and no issue, then I >> tried "rdnc reload" to be sure rndc was used, still no issue. >> >> By no issue I don't mean log are clean, I mean the DNS service is working >> well (tested using dig commands). >> >> In my logs I have the very same complaints about "duplicate zone" which >&...

...t;>> Hi Roger, >>> >>> I'm using Samba as AD DC in version 4.5.0 on Centos 7 with Bind9_DLZ DNS >>> backend, Bind is 9.9.4 and I don't have that issue. >>> I tried reload my bind using systemctl at first and no issue, then I >>> tried "rdnc reload" to be sure rndc was used, still no issue. >>> >>> By no issue I don't mean log are clean, I mean the DNS service is working >>> well (tested using dig commands). >>> >>> In my logs I have the very same complaints about "duplicate zo...