similar to: dns query not giving back all registers

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]:

Hi, I just did a new provision of my samba domain and now the formerly working bind 9.10 + dlz setup does no longer work. When trying to start bind9 it quits with the following error: named[5818]: samba_dlz: started for DN DC=mydomain,DC=de named[5818]: samba_dlz: starting configure named[5818]: dns_rdata_fromtext: buffer-0x7f9bc9231ec0:1: near 'srv2..': empty label named[5818]: Failed

I just upgraded bind9 on my backup DC to 9.9.5-7-Debian and restarting the service failed: 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'

Hello $LIST, i setup a new clean domain to examine the feature of updating/creating PTR records. When i call ipconfig /registerdns on the client i get this entry in the windows eventlog (sorry german) Fehler beim Registrieren der Hostressourceneinträge (A oder AAAA) für den Netzwerkadapter mit den folgenden Einstellungen: Adaptername: {2A467E48-624B-4CCF-9B7D-9BA5629D8117}

Hai,   I've checked out the log you send and i re-read the complete thread.   Based on thats done and what i did see in you logs now, looks like a  * (wildcard)  entry is giving the problem. But i am not sure of that, the wildcard bugs should be fixed, when i look in bugzilla.  (#10435 #12952 )   I've forwarded the mail to Rowland also before we go throw things at you again. ;-)

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

I am trying to setup dynamic updates with bind_dlz backend, but for some reason if any windows client or linux with nsupdate tries to remove AAAA record, server just 'cancelling transaction', while A and PTR records (both on reverse ipv4 and ipv6) working fine. If i'am remove AAAA record manually via samba-tool or windows mmc then AAAA record can be updated, but after that it again

Il giorno lun, 04/12/2017 alle 12.07 +0000, Rowland Penny via samba ha scritto: > Is the DHCP server updating the records for you ? Yes, but for now the problem is not dhcp (see follow) > If so, you need to stop the windows clients trying to update their > own records, they don't own them. I have the problem when join to domani via samba on another server, or when I run

Hello, I hope that someone can perhaps assist me or just guide me in the right direction. I've been following all the steps for setting up and migrating my Samba Internal DNS to Bind9_DLZ. https://wiki.samba.org/index.php/Setting_up_a_BIND_DNS_Server https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End But this doesn't seem to work for me, I can get bind started up 100% when I remove

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

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, running on Debian jessie 64bit samba 4.0.8 and bind 9.9 but with the description from https://wiki.samba.org/index.php/Dns-backend_bind I run into the following problem: # named -u bind -g 2>&1 |tee named.log 12-Sep-2013 15:43:07.287 starting BIND 9.9.3-rpz2+rl.13214.22-P2-Debian-1:9.9.3.dfsg.P2-4 -u bind -g 12-Sep-2013 15:43:07.287 built with '--prefix=/usr'

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

Il giorno lun, 04/12/2017 alle 11.29 +0000, Rowland Penny via samba ha scritto: > Try changing the 'options' of named.conf to this: Thanks Rowland Integrated your suggested changes and restart samba and named Now my named.conf is this[1], but none is change: [ root at server-addc ~]# samba_dnsupdate --all-names --fail-immediately update failed: REFUSED dic 04

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

> There doesn't seem anything wrong there, the only comment I would make, > is '/var/lib/samba/bind-dns/named.conf' pointing to the correct version > of named ? Yes cat /var/lib/samba/bind-dns/named.conf dlz "AD DNS Zone" { # For BIND 9.8.x # database "dlopen /usr/lib64/samba/bind9/dlz_bind9.so"; # For BIND 9.9.x database "dlopen

Hai, > > > > have rejoined all my DC's with new names, see below. > >;; ANSWER SECTION: > ><domain>.corp. 3600 IN NS psad101zatcrh.<domain>.corp. -> New > >rebuild, new hostname, RHEL6 to RHEL7 upgrade .... > > > > Led me to believe this is your problem. However, you say it works on > > one DC, but not with multiple

Hello there. I hope I'm in the right place for some Samba AD advice. I recently added two extra ADs to a setup I inherited. Originally there was a single Samba AD with BIND9_DLS config. DHCP was separate. Subsequently I installed Samba on two Raspberry Pis to act as backup servers. Basically, I followd this set of instructions:

Hello Rowland, I have already checked and the DN's are in AD, see attached. SOA: <domain>.corp. 3600 IN SOA psad102zadprh.<domain>.corp. . 9766 3600 600 86400 3600 See below NS, but the 1st NS (zatprdc001) doesn't exsit, and I cannot find it anywhere. NS: <domain>.corp. 3600 IN NS zatprdc001.<domain>.corp. <domain>.corp. 3600

Hi Rowland thanks for your response. I'm running samba 4.5.0rc1 on CentOS 7.2 I've dumped the DNS records, and it doesn't appear to have any SRV or NS records. Also the SOA record is pointing at the wrong server dc03 instead of dc01. I'm pretty sure it can be fixed, but I don't know how or what to do On 27 September 2016 at 07:59, Rowland Penny via samba < samba at