similar to: bind9 lockup problem

On 09/01/2023 14:35, Arnaud FLORENT via samba wrote: > Hi everyone and best wishes for 2023 > > > I think i'm facing the bind 9 DLZ lockup problem described here: > > https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End#The_Lockup_Problem > > > running samba 4.16 AD on ubuntu 20.04 with bind 9.16.15 > > there are about 500 computers on the network.

Dear list, we use debian stretch with Louis's 4.10.5 packages and bind9_dlz backend. There are two AD DCs with redundant ISC DHCP servers on them. The DHCP servers are updating the DNS along the lines of https://wiki.samba.org/index.php/Configure_DHCP_to_update_DNS_records_with_BIND9 but with nsupdate commands replaced by suitable calls to "samba-tool" (I had problems getting the

Yesterday I had an issue with Samba v 4.13.0. Went to backup and discovered backup computer has a drive failure and backup is gone. Only resort is to rebuild the DC. I cannot figure out why bind9 will not "host -t SRV _ldap._ tcp.ad.dtntwk.work." or "host -t SRV _kerberos._udp.ad.dtntwk.work." root at dc1:~# host -t SRV _ldap._tcp.subdom.example.com. >

Hi everyone, I have a question: is possible use BIND9 as DNS backend on a new Samba DC that will join into a domain where there are Samba DCs are using Samba Internal DNS server? I know that is a trivial question for someone, but I've followed steps described on wiki's topic "Joining a Samba DC to an Existing Active Directory" and in "Preparing the Host for Joining the

I am working on my second Ubuntu 16.04.1LTS running Samba 4.5.0 with Bind9_DLZ. I have one machine just like this one. Same hardware, same software setup. First machine is working fine. At the moment this (second) machine is not joined to the other (until I get Bind running.) I have searched log complaints. Compared settings between the two machines and despite bind running on the first one,

On 2016-10-16 12:55, Rowland Penny via samba wrote: > On Sun, 16 Oct 2016 12:38:00 -0500 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> I am working on my second Ubuntu 16.04.1LTS running Samba 4.5.0 with >> Bind9_DLZ. >> >> I have one machine just like this one. Same hardware, same software >> setup. First machine is

Hi Rowland, The samba-tool dns zonelist 127.0.0.1 -U Administrator%xxxxxxxxxx | grep 'pszZoneName', gives Using binding ncacn_ip_tcp:127.0.0.1[,sign] Mapped to DCERPC endpoint 135 added interface eth0 ip=192.168.117.10 bcast=192.168.14.255 netmask=255.255.255.0 added interface eth0 ip=192.168.117.10 bcast=192.168.14.255 netmask=255.255.255.0 Mapped to DCERPC endpoint 1024 added interface

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

Hi Rowland, Thank you. I think the 5 zones maybe a parsing issues somewhere. Also, the realms are in capital, must have been a typo. The UFW has been disabled and selinux is in a disbaled state /etc/bind/named.conf.options has options { directory "/var/cache/bind"; // If there is a firewall between you and nameservers you want // to talk to, you may need to

> > I repeat, Bind 9.12.x is unsupported at this time, just because it > worked once is no reason to use it. It may have nothing to do with your > problem, but using a supported Bind version will rule it out. Ok. :) I'll reinstall using supported version 9.11.3-2 OK, your server, but I think you should be aware that I have been using > Bind9 with Samba since December 2012

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

I had left my config alone for now and dhcp still writes to DOMAIN1.SUBDOMAIN.TLD. But samba has been complaining about not being able to write to bind in its zone. [2016/05/27 07:30:06.738434, 0] ../source4/dsdb/dns/dns_update.c:295(dnsupdate_nameupdate_done) ../source4/dsdb/dns/dns_update.c:295: Failed DNS update - NT_STATUS_UNSUCCESSFUL If you are right about it using kerberos I think I am

On Fri, May 27, 2016 at 10:23 AM, Rowland penny <rpenny at samba.org> wrote: > On 27/05/16 17:11, Jeff Sadowski wrote: > >> https://wiki.samba.org/index.php/Configure_BIND_as_backend_for_Samba_AD >> helped me find that I needed to add >> >> options { >> [...] >> tkey-gssapi-keytab "/usr/local/samba/private/dns.keytab"; >>

https://wiki.samba.org/index.php/Configure_BIND_as_backend_for_Samba_AD helped me find that I needed to add options { [...] tkey-gssapi-keytab "/usr/local/samba/private/dns.keytab"; [...] }; That seems to have fixed my errors with DNS On Fri, May 27, 2016 at 9:26 AM, Rowland penny <rpenny at samba.org> wrote: > On 27/05/16 14:37, Jeff Sadowski wrote: >

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

Sorry, Louis, not all of us use systemd. > Almost Harry... > > For debian Stretch. # cat /etc/debian_version buster/sid # cat /proc/1/cmdline /sbin/init You see: good old init. Just a test machine for a scheduled upgrade. > systemctl cat bind9 > # /lib/systemd/system/bind9.service > [Unit] > Description=BIND Domain Name Server > Documentation=man:named(8) >

> > Hmm, bind 9.12.x isn't supported yet. He works with "dlopen /usr/lib/x86_64-linux-gnu/samba/bind9/dlz_bind9_11.so" without problems, at first. include "/etc/bind/rndc.key"; > controls { > inet 127.0.0.1 allow { localhost; } keys { rndc-key;}; > }; > You do not need the four lines above Ok, but if I leave it, does not have problems

Set auth-nxdomain yes; And stop/start bind9 Other source : https://blogs.technet.microsoft.com/teamdhcp/2015/09/10/a-description-of-the-dns-dynamic-update-message-format/ /snap The DNS Client and Server services support the use of dynamic updates, as described in Request for Comments (RFC) 2136, "Dynamic Updates in the Domain Name System." The DNS Server service allows dynamic

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

I am considering which DNS implementation and cannot determine exactly when someone should use the Bind9 manner with BIND9_DLZ Module. For my purposes, I will have AD and non-AD nodes on the network using either DHCP or static IP addresses. Some will be Windows & Linux clients joined on the Samba AD domain for logins. Some will be Windows & Linux clients that are standalone using