similar to: samba_dlz Failed to configure reverse zone

And some more information about this strange effect apparently no-one has seen before. I now added the missing zone: samba-tool dns zonecreate verdandi 10.16.172.in-addr.arpa -U Administrator and it claims that the zone is okay, but the next one is missing: Dec 29 10:31:12 verdandi named[2601]: Loading 'ad.microsult.de' using driver dlopen Dec 29 10:31:12 verdandi named[2601]:

Last month I struggled with a severe DLZ issue and today I could solve it. Credits for the important idea go to Peter Serbe, thanks! I checked the DNS contents using RSAT. There was nothing wrong with SOA nor NS entries, but the reverse zones were actually forward zones with proper names in the in-addr.arpa. domain. I built proper reverse zones and deleted the forward-reverse zones and Bind

Dear Roland, and here we have one reasons / prove regarding Debian and current Samba BIND DLZ issues : http://metadata.ftp-master.debian.org/changelogs//main/b/bind9/bind9_9.8.4.dfsg.P1-6+nmu2+deb7u3_changelog MSG >> " * disable dlz until we get a patch to make it build again" Well Debian Maintainers seems seeking missing the dlz patches that RHEL & SLES maintainers created

On 29/12/14 09:40, Lars Hanke wrote: > And some more information about this strange effect apparently no-one > has seen before. > > I now added the missing zone: > > samba-tool dns zonecreate verdandi 10.16.172.in-addr.arpa -U > Administrator > > and it claims that the zone is okay, but the next one is missing: > > Dec 29 10:31:12 verdandi named[2601]: Loading

I dug somewhat deeper into what is going on below and it seems even stranger. The reverse zone without SOA or NS does not even exist: root at verdandi:~# samba-tool dns query localhost 10.16.172.in-addr.arpa @ ALL -U Administrator Password for [AD\Administrator]: ERROR(runtime): uncaught exception - (9714, 'WERR_DNS_ERROR_NAME_DOES_NOT_EXIST') File

Hello , review bind9 options ... >> Dec 22 12:25:55 verdandi named[18534]: starting BIND 9.9.5-7-Debian -u >> bind -4 >> Dec 22 12:25:55 verdandi named[18534]: built with '--prefix=/usr' >> '--mandir=/usr/share/man' '--infodir=/usr/share/info' >> '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads'

Just to clarify some things ... the Bind9 and Samba4 are both current Debian Jessie on amd64. So the applicable changelog would be http://metadata.ftp-master.debian.org/changelogs//main/b/bind9/testing_changelog Using 1:9.9.5.dfsg-6 the system worked nicely. Fixing a CVE pertaining to recursion does not easily link to DLZ issues. The system definitely has DLZ included. Otherwise it could not

Dear Rowland , Just keep in mind that the Debian RPI maintated by rasperry.org PI fellows and _not_ mainly by the Mainsteam debian pkg maintainers, and ways behind the main distro - allmost. > > Even though there is no mention of dlopen, samba_dlz works. > yes/no ->> its not displaying the DLZ file open <<- and that happen even on my now +1J old samba4.0 RPI samba4 ad.

After deletion and recreation of the reverse zone Bind9 started again. Thanks to Rowland for the hint. However, bind complains that virtually all zones are duplicate and thus at least one issue is ignored. Since it's samba_dlz complaining there's either something wrong in the AD or in the DLZ module. The Bind does not have any other zones than the DLZ. I have trouble connecting

On 29/12/14 16:25, support at remsnet.de wrote: > Hello , > > review bind9 options ... > >>> Dec 22 12:25:55 verdandi named[18534]: starting BIND 9.9.5-7-Debian -u >>> bind -4 >>> Dec 22 12:25:55 verdandi named[18534]: built with '--prefix=/usr' >>> '--mandir=/usr/share/man' '--infodir=/usr/share/info' >>>

On 29/12/14 17:32, support at remsnet.de wrote: > Dear Rowland , > > Just keep in mind that the Debian RPI maintated by rasperry.org PI fellows and _not_ mainly by the Mainsteam debian > pkg maintainers, and ways behind the main distro - allmost. > >> Even though there is no mention of dlopen, samba_dlz works. >> > yes/no ->> its not displaying the DLZ file

Hi Marc, >> The cause is that the password change didn' reach both AD DCs, but only >> one. The other one still had the old value as could be seen by >> samba-tool ldapcmp. Restarting the DCs and waiting for a couple of >> seconds brings them back to sync and Windows logons work as they used to. >> Any idea, what I should do next time to obtain valuable output

On 29/12/14 18:20, support at remsnet.de wrote: > Dear Roland, > > and here we have one reasons / prove regarding Debian and current Samba BIND DLZ issues : > http://metadata.ftp-master.debian.org/changelogs//main/b/bind9/bind9_9.8.4.dfsg.P1-6+nmu2+deb7u3_changelog > MSG >> " * disable dlz until we get a patch to make it build again" > > Well Debian

Hi, named exited when loading 'AD DNS Zone': Feb 03 17:46:43 ID-01 named[4498]: Loading 'AD DNS Zone' using driver dlopen Feb 03 17:46:43 ID-01 named[4498]: samba_dlz: started for DN DC=elephanttalk,DC=cn Feb 03 17:46:43 ID-01 named[4498]: samba_dlz: starting configure Feb 03 17:46:43 ID-01 named[4498]: zone 30.168.192.in-addr.arpa/NONE: has 0 SOA records Feb 03 17:46:43 ID-01

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

Hi, I removed a couple of dead DC's from my domain using this command: samba-tool domain demote --remove-other-dead-server=<dc name> I then restarted named on the remaining server, but it failed to start with the following errors in messages: named[30255]: samba_dlz: configured writeable zone 'x.x.x.in-addr.arpa' named[30255]: samba_dlz: configured writeable zone

Hello, I have two samba 4.2.7-SerNet-Debian-8.wheezy AD servers. since few days now I have some winbind errorsthat block the server... It seems that they appears more and more frequently... ( about one time per day ) I have about 200 clients pc with windows 10, seven and XP. Last month I've migrated about 30 pc from seven to 10. Is there a relationship? In the following logs, you can see

After having compiled samba-4.4.0 and installed bind9 and isc-dhcp-server from Debian repos 8 everything works fine except that no reverse zone updates from DHCP to DNS. I tried the example that comes in https://wiki.archlinux.org/index.php?title=Samba_4_Active_Directory_domain_controller&oldid=427930 This is the error that but I have not managed to solve April 12 16:22:45 cd1 named [848]:

Hello, I have the following problem with my bind9 together with samba 4.9 SerNet. If I start the bind9 I got the following error-message: --------------- Oct 15 20:35:50 addc2 named[2269]: Loading 'AD DNS Zone' using driver dlopen Oct 15 20:35:50 addc2 named[2269]: samba_dlz: started for DN DC=zfd,DC=forumzfd,DC=de Oct 15 20:35:50 addc2 named[2269]: samba_dlz: starting configure Oct 15

Hi samba team ! I'm face with a new problem on a new Samba PDC install (Debian 9). I don't know why, but systemd run multiples "rndc reconfig" commands during the init script. So the bind9 log file show : -> A successful start -> A failed reconfig (samba_dlz Ignoring duplicate zone) at each boot/reboot. So I need to restart bind9 each time manually. I created a wrapper