similar to: DNS Update not working after update to 4.5.3

I suspect a zone overlap. Did you add an extra zone manualy in bind? Or something like this... You added : Zone1.Domain.TLD and then Domain.TLD But then with the reverse zones. Because this : > Jan 20 13:58:09 samba02 named[10811]: zone 2.168.192.in-addr.arpa/NONE: > has no NS records Does not look likes the samba_DLZ log lines but a pure bind log line. Review you bind config and

Hai,   Seeing : > Jan 23 14:55:40 samba01 named[3279]: samba_dlz: configured writeable > zone '168.192.in-addr.arpa' > Jan 23 14:55:40 samba01 named[3279]: zone local.laurenz.ws/NONE: has no > NS records > Jan 23 14:55:40 samba01 named[3279]: samba_dlz: Failed to configure zone > 'local.laurenz.ws'   Normaly you should see first the local.laurenz.ws

i will do so.... thanks Am 25.01.2017 um 08:46 schrieb L.P.H. van Belle via samba: > Still > > Check this line from you named config. > > include "/etc/bind/named.conf.default-zones"; > > This can cause an overlap in the zones, so be carefull with that one. > > > Greetz, > > Louis > > >> -----Oorspronkelijk bericht----- >> Van: samba

Hi, i reduced to one reverse dns zone (192.168.x.x.) same error when converting internal to bind_dlz Jan 23 14:55:39 samba01 named[3279]: Loading 'AD DNS Zone' using driver dlopen Jan 23 14:55:40 samba01 named[3279]: samba_dlz: started for DN DC=local,DC=laurenz,DC=ws Jan 23 14:55:40 samba01 named[3279]: samba_dlz: starting configure Jan 23 14:55:40 samba01 named[3279]: samba_dlz:

hmm, just a guess: i have two reverse lookup zones: 192.168.2.x 192.168.6.x defined. should i define 192.168.x.x instead? Am 20.01.2017 um 15:21 schrieb L.P.H. van Belle via samba: > I suspect a zone overlap. > Did you add an extra zone manualy in bind? > > Or something like this... You added : > Zone1.Domain.TLD and then > Domain.TLD > > But then with the reverse

it doesn't matter, problem is with both backends... Am 18.01.2017 um 18:03 schrieb Marc Muehlfeld: > Hi Dirk, > > Am 18.01.2017 um 08:51 schrieb Dirk Laurenz via samba: >> [2017/01/18 08:31:18.113146, 0] >> ../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done) >> >> ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error >>

Still Check this line from you named config. include "/etc/bind/named.conf.default-zones"; This can cause an overlap in the zones, so be carefull with that one. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Dirk Laurenz via > samba > Verzonden: woensdag 25 januari 2017 1:26 > Aan: samba at

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}

----- Original Message ----- | Hi Felipe, | Am 25.01.2017 um 14:16 schrieb Felipe_G0NZÁLEZ_SANTIAG0 via samba: | > I provisioned a server with Samba4.3 from repo ubuntu16.04. | > I tested some things, but I can NOT connect to my Samba DC from the Windows | > DNS client. | > ADUC, AD Sites and services, and AD Domain & Trusts, connects Ok. | > But DNS [" Acces is Denied

----- Original Message ----- | Hi, | Am 25.01.2017 um 16:37 schrieb Felipe_G0NZÁLEZ_SANTIAG0 via samba: | > | * Anything appears in the logs when it fails? Increase log level, if | > | necessary. | > Well, I don't know if this is useful, but only I see is this in the | > /var/log/syslog file: | > Jan 25 01:15:08 ubuntus samba[27351]: [2017/01/25 01:15:08.780106, 0] | >

On Mon, 15 May 2017 22:02:30 +0200 "Dirk Laurenz" <samba at laurenz.ws> wrote: > Any idea? > > > > root at samba01:~# uname -a > Linux samba01 4.9.14-v7+ #977 SMP Mon Mar 13 18:25:19 GMT 2017 armv7l > GNU/Linux > > root at samba01:~# cat /etc/debian_version > 8.7 > > root at samba01:~# samba -V > Version 4.6.3 I take that you have built

Hello, i just setup a new samba domain, setting up the second dc failes. I compiled the second dc myself and the first join failed due to a missing directory (var/lib/samba/private) I created it and the called the join command again... But now the dc seems to exist, but is not visible in domain tools or ldbedit. But I get this message. What entry is meant here? Is the out put of

Hi, i want to move my DC from an amd64 debian jessie to a armhf debian jessie. My first guess is to demote the dc and rejoin the new server. Der DC has all FSMO roles and is part of a three DC setup. Would this be the right way or should i choose another way? Regards, Dirk

Same error here... root at samba01:~# samba-tool ldapcmp ldap://samba01 ldap://samba02 -Uadministrator --filter=CN,DC,member CONFIGURATION Password for [LAURENZ\administrator]: * Comparing [CONFIGURATION] context... * Objects to be compared: 1631 Comparing: 'CN=SAMBA03,CN=Servers,CN=Harz,CN=Sites,CN=Configuration,DC=local,DC=laurenz,DC=ws' [ldap://samba01]

moving to a temporary server could help? what i mean is: trasnfer fsmo roles to samba02 join temp01 demote old samba01 bring up new samba01 join samba01 remote temp01 correct? this should work? Am 27.10.2016 um 13:09 schrieb Rowland Penny via samba: > On Thu, 27 Oct 2016 11:10:58 +0200 > Dirk Laurenz via samba <samba at lists.samba.org> wrote: > >> Hi, >>

Hello, I'm in trouble here with what appears to be a total meltdown of my DNS on my Domain Controllers. I only have two DCs right now and I cannot resolve anything on either of them. I am on Ubuntu 16.04 with a compiled version of Samba 4.10.4. I also have a compiled version of BIND 9.10.3-P4-Ubuntu <id:ebd72b3> # service bind9 status ? bind9.service - BIND Domain Name Server ?

I'm trying to troubleshoot why our workstations have stopped dynamically registering their ip addresses in our AD using bind_dlz setup. It worked for a couple of months and now does not. I realized I have a basic question about how it is supposed to work. Do the workstations (after getting a dynamic address from the dhcpd server) contact the AD DC directly with the information? Or does dhcpd

Hi, All 3 of my DCs regularly display an error in syslog almost exactly every 10 minutes. They have been doing this for quite some time, and I have so far ignored the message as everything else DNS-wise seemed to mostly be working - but I figured it was worth getting to the bottom of it if I can. So this isn't new at all but rather something that has been present for some time. I am using

Hello there. I have a setup with Samba AD and a Named backend. Everything has been working fine, until a few days ago, I cannot start the DNS snap-in from windows. I get a dialog box saying "Access was denied. Would you like to add it anyway?" If I enable level 3 debugging in the samba.conf, I get the following: [2017/05/11 07:25:30.413481, 3]

Hai, ? Just a tip for the people reading the list. ? if you see Failed DNS update - NT_STATUS_IO_TIMEOUT? or messages : ?RPC unavailable if you connect from windows client to the samba AD DC server ? Read this. ? I have a "test' AD DC on a XEN server running and this DC does nothing. 1 pc ( win7) is joined, some dns recored are set, nothing special.. ? today i checked the logs, and