[Samba] samba dlz. bind9 nslookup is wrong

Patrik alabard at gmail.com
Mon Aug 5 11:58:10 UTC 2019


root at server:~# cat /etc/resolv.conf
search p3x-dc.patrikx3.com
nameserver 192.168.78.20
nameserver 2001:470:1f1b:5b3:21b:21ff:fea6:ce93
root at server:~#

I have a server with 2 nics and 2 routers, each subnets are 192.168.78.0/24
| 2001:470:1f1b:5b3::/64 and the other is 192.168.81.0/24
| 2001:470:1f1b:5b5::/64

But no matter what I set, Samba generates via DLZ a unknown ip address
192.168.81.120, which is no-one, the server (before is uses 192.168.81.20)
but sometime it just generated this >

root at server:~# nslookup server.p3x-dc.patrikx3.com
Server:         192.168.78.20
Address:        192.168.78.20#53


*Name:   server.p3x-dc.patrikx3.com
<http://server.p3x-dc.patrikx3.com>Address: 192.168.81.120*
Name:   server.p3x-dc.patrikx3.com
Address: 192.168.78.20
Name:   server.p3x-dc.patrikx3.com
Address: 2001:470:1f1b:5b3:21b:21ff:fea6:ce93

*Name:   server.p3x-dc.patrikx3.com
<http://server.p3x-dc.patrikx3.com>Address:
2001:470:1f1b:5b5:eeaa:a0ff:fe1b:4d84*
Name:   server.p3x-dc.patrikx3.com
Address: 2001:470:1f1b:5b3::20




*Patrik*
WWW <https://patrikx3.com> | GitHub <https://github.com/patrikx3/> | NPM
<https://www.npmjs.com/~patrikx3> | Corifeus <https://corifeus.com> | +36
20 342 8046




On Mon, Aug 5, 2019 at 1:51 PM L.P.H. van Belle via samba <
samba at lists.samba.org> wrote:

> That is because your resolving setup is wrong.
>
> You problem starts here.
> Checking file: /etc/resolv.conf
>
> search patrikx3.com
> search corifeus.com
> search p3x-dc.patrikx3.com
>
> The first 2 will do nothing, only last will be used that setup.
>
> You want :
> search p3x-dc.patrikx3.com patrikx3.com corifeus.com
> But still thats not needed, you only need.
> search p3x-dc.patrikx3.com
>
> Because the other domains are resolved through dns.
>
> So, always your primary dnsdomain first. (the one where you samba AD-DC is
> configured with )
> P.s. You forgot the hide the pass in named output ( key signed_comms ) so
> change that.
>
> But before we can give a good advice.
>
> Is the server directly on the internet ( 1 nic/2nics )
> Or
> Is the server on the internet and LAN (2 nics)
> Or
> Is the server on the LAN only but accessable for the internet through
> proxy.
>
> What is the servers main thing it should do.
>
> Give me above and i'll see if i can give you an good advice here.
>
>
> Greetz,
>
> Louis
>
>
>
> > -----Oorspronkelijk bericht-----
> > Van: samba [mailto:samba-bounces at lists.samba.org] Namens
> > Patrik via samba
> > Verzonden: maandag 5 augustus 2019 13:38
> > Aan: Rowland penny
> > CC: sambalist
> > Onderwerp: Re: [Samba] samba dlz. bind9 nslookup is wrong
> >
> > the problem is that here:
> > root at server:~# nslookup p3x-dc.patrikx3.com
> > Server: 192.168.78.20
> > Address: 192.168.78.20#53
> >
> > Name: p3x-dc.patrikx3.com
> > Address: 192.168.78.20
> > Name: p3x-dc.patrikx3.com
> > *Address: 192.168.81.120*
> > Name: p3x-dc.patrikx3.com
> > *Address: 2001:470:1f1b:5b5:eeaa:a0ff:fe1b:4d84*
> > Name: p3x-dc.patrikx3.com
> > Address: 2001:470:1f1b:5b3:21b:21ff:fea6:ce93
> > Name: p3x-dc.patrikx3.com
> > Address: 2001:470:1f1b:5b3::20
> >
> > *if should at least show like:*
> > root at server:~# nslookup p3x-dc.patrikx3.com
> > Server: 192.168.78.20
> > Address: 192.168.78.20#53
> >
> > Name: p3x-dc.patrikx3.com
> > Address: 192.168.78.20
> > Name: p3x-dc.patrikx3.com
> > *Address: 192.168.81.20*
> > Name: p3x-dc.patrikx3.com
> > *Address: **2001:470:1f1b:5b5:21b:21ff:fea6:ce92*
> > Name: p3x-dc.patrikx3.com
> > Address: 2001:470:1f1b:5b3:21b:21ff:fea6:ce93
> > Name: p3x-dc.patrikx3.com
> > Address: 2001:470:1f1b:5b3::20
> >
> > *But for unknown reason it generates a 192.168.81.120 instead
> > (or not at
> > all) 192.168.81.20 as that is the server ip addres
> > (**192.168.81.20 and *
> > *2001:470:1f1b:5b5:21b:21ff:fea6:ce92**)*
> > *All my windows clients are registered in my p3x-dc domains
> > and i can log
> > in. i will explore in the adexplorer what something could
> > cause this. but
> > it is very weird. it would be cool if someone would know what it could
> > happen.*
> >
> >
> >
> >
> > *Patrik*
> > WWW <https://patrikx3.com> | GitHub
> > <https://github.com/patrikx3/> | NPM
> > <https://www.npmjs.com/~patrikx3> | Corifeus
> > <https://corifeus.com> | +36
> > 20 342 8046
> >
> >
> >
> >
> >
> > On Mon, Aug 5, 2019 at 1:28 PM Rowland penny via samba <
> > samba at lists.samba.org> wrote:
> >
> > > On 05/08/2019 11:53, Patrik wrote:
> > > > the    file "/etc/bind/zones/enp1s0f3/patrikx3.com
> > > > <http://patrikx3.com/>"; are my domain names A, AAAA,
> > CNAME-s, that is
> > > > where i store then, there is know AD records at all. it
> > is all DLZ.
> > > > *_
> > > > _*
> > >
> > > If 'patrikx3.com' is a registered dns domain name, then you
> > should have
> > > used a subdomain of this for the AD dns domain.
> > >
> > > The file you refer to is a FLATFILE and you SHOULDN'T be
> > storing your AD
> > > dns records there and it ISN'T bind9_dlz.
> > >
> > > Rowland
> > >
> > >
> > >
> > > --
> > > To unsubscribe from this list go to the following URL and read the
> > > instructions:  https://lists.samba.org/mailman/options/samba
> > >
> > --
> > To unsubscribe from this list go to the following URL and read the
> > instructions:  https://lists.samba.org/mailman/options/samba
> >
> >
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>


More information about the samba mailing list