similar to: Internal DNS migrate to Bind9_DLZ

Hai, Did you make sure that your root and localhost zones are loaded last in the bind config. The order matters, at least if you also use bind_DLZ. I suggest, you try it. Im Just thinking about this, if your . (root) zone is loaded, and its trying to lookup you company.corp domain. It hits resolv.conf then you bind, and bind_dlz is not loaded yet, so lookup on the internet. Its a possible

It is part of the Sernet packages and is currently on 1.3.4 /usr/lib64/samba/libldb.so.1.3.4 We started using sernet-samba-ad from v4 using the internal dns and updated as versions were released. We have now recently updated from 4.8.2 to 4.8.3 and still using internal dns. Our DNS is working as it should, it's only been since recently that we have to migrate to bind9. On Mon, Jul 30, 2018

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. ;-)

Yes I have added "server services = -dns" to my smb.conf file and also removed "dns forwarder =" I've done the same setup but on Samba 4.7.7, RHEL6, named 9.8 and this works perfect. On Mon, Jul 30, 2018 at 11:18 AM Rowland Penny via samba < samba at lists.samba.org> wrote: > On Mon, 30 Jul 2018 10:57:11 +0200 > Eben Victor <eben.victor at gmail.com>

Hello Rowland, Please see below installed samba packages. # rpm -qa | grep samba sernet-samba-client-4.8.3-11.el7.x86_64 sernet-samba-common-4.8.3-11.el7.x86_64 sernet-samba-libsmbclient0-4.8.3-11.el7.x86_64 sernet-samba-4.8.3-11.el7.x86_64 sernet-samba-ad-4.8.3-11.el7.x86_64 sernet-samba-libs-4.8.3-11.el7.x86_64 sernet-samba-winbind-4.8.3-11.el7.x86_64 ldb is installed with the samba packages.

On Mon, 30 Jul 2018 10:57:11 +0200 Eben Victor <eben.victor at gmail.com> wrote: > Hello Rowland, > > See below as requested. > > /etc/named.conf > # Global Configuration Options > > include "/var/lib/samba/bind-dns/named.conf"; > > options { > > dump-file "/var/named/data/cache_dump.db"; > statistics-file

On Wed, 31 Oct 2018 18:36:52 +0200 Eben Victor <eben.victor at gmail.com> wrote: > 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

Hello Rowland, See below as requested. /etc/named.conf # Global Configuration Options include "/var/lib/samba/bind-dns/named.conf"; options { 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"; auth-nxdomain yes; directory

Hi Rowland, I didn't build samba, I'm running the sernet packages, # rpm -qa | grep sernet sernet-samba-libsmbclient0-4.8.6-16.el7.x86_64 sernet-samba-ad-4.8.6-16.el7.x86_64 sernet-samba-libs-4.8.6-16.el7.x86_64 sernet-samba-client-4.8.6-16.el7.x86_64 sernet-samba-winbind-4.8.6-16.el7.x86_64 sernet-samba-common-4.8.6-16.el7.x86_64 sernet-samba-4.8.6-16.el7.x86_64 I don't mind having

On Wed, 31 Oct 2018 23:34:38 +0200 Eben Victor <eben.victor at gmail.com> wrote: > Hi Rowland, > > I didn't build samba, I'm running the sernet packages, > # rpm -qa | grep sernet > sernet-samba-libsmbclient0-4.8.6-16.el7.x86_64 > sernet-samba-ad-4.8.6-16.el7.x86_64 > sernet-samba-libs-4.8.6-16.el7.x86_64 > sernet-samba-client-4.8.6-16.el7.x86_64 >

On Mon, 30 Jul 2018 10:41:14 +0200 Eben Victor via samba <samba at lists.samba.org> wrote: > 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 >

On Mon, 30 Jul 2018 15:42:45 +0200 Eben Victor <eben.victor at gmail.com> wrote: > Hello Rowland, > > selinux has been disabled, I also ran th follow > > # systemctl stop sernet-samba-ad > # samba_upgradedns --dns-backend=BIND9_DLZ > # named -d3 -f -g -u named > > Which then still fails, see below smb.conf > > [global] > workgroup = DOMAIN

On Thu, 1 Nov 2018 07:21:57 +0200 Eben Victor <eben.victor at gmail.com> wrote: > I've been been trying to investigate this for sometime now, hence I > came to the experts :) > > I have rejoined all my DC's with new names, see below. > ;; ANSWER SECTION: > <domain>.corp. 3600 IN NS psad101zatcrh.<domain>.corp. -> > New rebuild, new

> So, you are using Samba without problem, it is just that when you try > to use Bind9 instead of the internal dns server, your problems start. > > Let's just recap > > You have run 'samba_upgradedns' > You have altered smb.conf > You have configured 'named.conf' correctly > The Samba 'named.conf' file is readable by 'named' (this

Hello Rowland, selinux has been disabled, I also ran th follow # systemctl stop sernet-samba-ad # samba_upgradedns --dns-backend=BIND9_DLZ # named -d3 -f -g -u named Which then still fails, see below smb.conf [global] workgroup = DOMAIN realm = DOMAIN.CORP netbios name = PDC server role = active directory domain controller idmap_ldb:use rfc2307 = yes

> > > 30-Jul-2018 10:26:40.027 samba_dlz: starting configure > > > 30-Jul-2018 10:26:40.049 dns_rdata_fromtext: buffer-0x7facd1f60dc0:1: > > > near eof: unexpected end of input > > > 30-Jul-2018 10:26:40.049 Failed to put rr > > > 30-Jul-2018 10:26:40.269 zone domain.corp/NONE: has 0 SOA records > > > 30-Jul-2018 10:26:40.269 zone

Hello Roland/Louis & All, All the best for the new year. Sorry to bring this up again. I finally managed to give some more attention to this issue of mine. I've set up a new test domain server, and I managed to seamless migrate from SAMBA_INTERNAL to BIND9_DLZ and the other way again. With a little help of new software we purchased, I exported all data from production and imported the

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

Thanks Roland, You are correct. Our Bind9 DLZ is version 9.9.4. I'll have to check if I will be able to upgrade to a newer version of Bind, these are on our production servers. On Mon, Jul 22, 2019 at 9:40 AM Rowland penny via samba < samba at lists.samba.org> wrote: > On 22/07/2019 08:24, Eben Victor via samba wrote: > > Hello All, > > > > I hope someone might be

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