similar to: DNS update fails after samba domain controller is restarted

Hi guys am needing some help, am using bind to provide the DNS backend for samba using dlz resolution works well however!! my clients are not able to update the registered DNS entries when running samba_dnsupdate against the samba DLZ named server am getting ; Communication with 127.0.0.1#53 failed: timed out could not talk to any default name server Failed nsupdate: 1 Then bind stops

Hai Maurik-Jan, Stefan's work can be found here, i'm reading it myself and its really good.

Hi Stefan, others, Just to report back that things work very nicely now that DNS is using one dns proxy that resolves both AD domains. I am testing now with a 'full' two-way trust, and everyhing seemed to work, including the tests from samba-tool and from windows "domains and trusts" perspective. From an administrative point of view, the fact that your have to add

Thanks everybody! The sudden burst of help (both on- and offlist) is much appreciated. :-) I'll get back to my test setup next week, and try again with these new insights. MJ On 2/28/19 3:46 PM, L.P.H. van Belle via samba wrote: > Hai Maurik-Jan, > > Stefan's work can be found here, i'm reading it myself and its really good. > >

On Fri, 1 Jun 2018 12:12:43 +0100 Zdravko Zdravkov <nirayah at gmail.com> wrote: > True that! Sorry > > smb.conf > > > > [global] > > netbios name = AD > > realm = XXXX.CO.UK > > server role = active directory domain controller > > server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, > >

Hi Rowland, 1. Thanks for you clarification ;) 2. About, my old DLZ configuration is: Versions: bind-9.11 - S.O Centos 7.8 This was the sambadc04 with the old bind dlz backend . [..........] [root at sambadc04 ~]# cat /etc/sysconfig/named |grep -v '^#' NAMED_RUN_CHROOTED="no" OPTIONS="-4" [..........] The /etc/named.conf [..........] acl "trusted" {

Hi Rowland. Trying the suggested named.conf broke the local resolve of the storage as well (for clients in 192.168.26.0), so I reverted back to my old one since I have computers here using the storage at the moment. Would you have any other suggestions? On Fri, Jun 1, 2018 at 1:04 PM, Rowland Penny via samba < samba at lists.samba.org> wrote: > On Fri, 1 Jun 2018 12:12:43 +0100 >

Hello Rowland, Thanks for your reply. This is my named.conf options { listen-on port 53 { 127.0.0.1; 192.168.1.10; }; directory "/var/named"; dump-file "/var/named/data/cache_dump.db"; statistics-file "/var/named/data/named_stats.txt"; memstatistics-file "/var/named/data/named_mem_stats.txt";

Resend. ________________________________ From: Turritopsis Dohrnii Teo En Ming <ceo at teo-en-ming-corp.com> Sent: Wednesday, February 19, 2020 8:07 AM To: samba at lists.samba.org <samba at lists.samba.org>; Rowland penny <rpenny at samba.org> Cc: Turritopsis Dohrnii Teo En Ming <ceo at teo-en-ming-corp.com> Subject: Re: [Samba] Why are ForeignSecurityPrincipals and

Resend. ________________________________ From: Turritopsis Dohrnii Teo En Ming <ceo at teo-en-ming-corp.com> Sent: Wednesday, February 19, 2020 8:09 AM To: samba at lists.samba.org <samba at lists.samba.org>; Rowland penny <rpenny at samba.org> Cc: Turritopsis Dohrnii Teo En Ming <ceo at teo-en-ming-corp.com> Subject: Re: [Samba] Why are ForeignSecurityPrincipals and

Hello! I use NSD 4.7.0 self compiled: Configure line: --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking

Hi, h when I have the following problem with rndc: [root at centos7 ~]# rndc recursing and rndc: 'recursing' failed: permission denied SELinux is disables: named.conf config file is: // // named.conf // // Provided by Red Hat bind package to configure the ISC BIND named(8) DNS // server as a caching only nameserver (as a localhost DNS resolver only). // // See

True that! Sorry smb.conf > [global] > netbios name = AD > realm = XXXX.CO.UK > server role = active directory domain controller > server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, > winbindd, ntp_signd, kcc, dnsupdate > workgroup = XXXX > idmap config XXXX:unix_nss_info = yes >

I am having a mail server problem where the mail to one domain is being sent to the wrong server. When I use "dig masonc.com mx", I get ;; ANSWER SECTION: masonc.com. 86400 IN MX 5 mail.masonc.com. ;; AUTHORITY SECTION: masonc.com. 86400 IN NS ns1.picadoo.com. masonc.com. 86400 IN NS ns2.picadoo.com. ;;

Hi Rowland, This is my full /etc/named.conf: // // named.conf // // Provided by Red Hat bind package to configure the ISC BIND named(8) DNS // server as a caching only nameserver (as a localhost DNS resolver only). // // See /usr/share/doc/bind*/sample/ for example named configuration files. // options { listen-on port 53 { any; }; listen-on-v6 port 53 { ::1; }; directory

Hello all, I?ve installed a proxy Squid in my gateway and a Cache DNS Server with bind. The problem is the server is only resolving is own querys but not the client queries from my company. When I do: $service named start I see in /var/log/messages: starting BIND 9.3.4-P1 -u named -t /var/named/chroot found 1 CPU, using 1 worker thread loading configuration from '/etc/named.conf'

Hi, I have 2 samba AD Dc's running 4.7.0 with bind_DLZ on both servers. For the most part things seem to be working as expected. I have created reverse zones as per https://wiki.samba.org/index.php/DNS_Administration#Creating_a_new_zone. I have noticed 2 things that seem odd. when I use the windows dns manager to add an A record. If I check the box that says to update the reverse zone and

I must have something mis-configured in my bond setup. Things are working, but I'm getting TONS of this sort of stuff in my log: +2001:502:ad09::4#53: 1 Time(s) network unreachable resolving 'kns1.kuwaitnet.net/A/IN': +2001:503:231d::2:30#53: 1 Time(s) network unreachable resolving 'kns1.kuwaitnet.net/A/IN': +2001:503:a83e::2:30#53: 1 Time(s) network unreachable

On 27/11/2019 23:57, S?rgio Basto wrote: > Thank you for the warning :) [1] , I'm fighting the same problem but I > have a different configuration that I never told you before , I'm > running my centos 7 packages (very similar to other fellows) [2] where > DC1 , DC2 and DC3 are running SambaAD, samba-4.8.8-2.el7.x86_64 with > BIND9_DLZ (bind-9.11.4-9.P2.el7.x86_64) . First

Hai, Ok, first, 15--03-2017 Rowland replied on your subject : "Re: [Samba] Problems with replication and dns" Did you try to setup that config exact as he did show? If not, and even if you did, below is your config, but adjusted, at least now it "usable" for the AD DC. So please setup this up, restart bind and post the log again. (more info :