[Samba] samba dlz. bind9 nslookup is wrong

Mon Aug 5 13:48:03 UTC 2019

not my tekst; source : https://networkengineering.stackexchange.com/questions/50843/what-are-the-reasons-for-seeing-an-incomplete-arp 

A successful ARP resolution is required for two IPv4 nodes to communicate on a common layer-2 segment (usually Ethernet).

Incomplete ARP requests have two basic reasons.

The ARP request has not been answered. 
Either the destination node hasn't received the ARP request or its response hasn't been received. The destination node may be down.

The source node's network mask is not configured correctly. The source node considers all destinations within its own subnet local or on-link: it expects to be able to talk to them directly over its Ethernet interface, without the help of a gateway router.

When e.g. a node within the 192.168.0.0/24 subnet is incorrectly set up with 192.168.0.10/16 it considers a destination like 192.168.16.1 local. It will not try to use a gateway but attempt a direct ARP which stays incomplete.
Whether the source or the destination/next hop node is a router, multi-layer switch or end node doesn't matter

So im expecting your saying the "host" is down. Because that ip is down. 

ip -s -s neigh flush all
arp -n 

and its gone. 

Restart nscd if running. 

Greetz, 

Louis

> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> Patrik via samba
> Verzonden: maandag 5 augustus 2019 15:02
> Aan: Rowland penny
> CC: samba at lists.samba.org
> Onderwerp: Re: [Samba] samba dlz. bind9 nslookup is wrong
> 
> I FOUND SOMETHING:
> 
> root at server:/# arp
> Address                  HWtype  HWaddress           Flags Mask
>  Iface
> 192.168.78.21            ether   e0:d5:5e:da:9c:3b   C
> enp1s0f3
> 192.168.78.90            ether   8c:eb:c6:53:19:00   C
> enp1s0f3
> 192.168.81.1             ether   62:38:e0:10:a7:eb   C
> enp1s0f2
> 192.168.78.40            ether   b4:6b:fc:95:39:54   C
> enp1s0f3
> 192.168.81.120                   (incomplete)
>  enp1s0f2
> 192.168.81.243           ether   b4:6b:fc:95:39:54   C
> enp1s0f2
> 192.168.78.1             ether   62:38:e0:bd:7a:68   C
> enp1s0f3
> 
> WHAT IS IT MEAN INCOMPLETE ARP? THIS MUST BE THE ISSUE!
> 
> *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 2:44 PM Patrik <alabard at gmail.com> wrote:
> 
> > what is weird is that i have not changed it for about 2 
> years, only apt
> > update, upgrade. no other change, ipv4 and ipv6 address 
> working correctly.
> > now there is this bug, that i have not changed anything and 
> suddenly, DLZ
> > generates an unknown not connected , working, live ip4 and ip6.
> > and all because it tried an nslookup p3x-dc.patrikx3.com 
> that was the
> > correct for over 2 years.
> > the only thing that is good, that it rotates the ip 
> addresses so it works,
> > but it is annoying. but i give up i spent 2 days looking 
> for thinks that
> > were working correct.
> > this 192.168.81.120 (unknown) was always my server ip 
> (192.168.78.20 and
> > 192.168.81.20 and the ipv6 as well)
> >
> > to me it looks fishy, i wait for bullseye ( i am only on 
> testing repo, but
> > until many packages are not upgraded to bullseye, i sticked 
> with buster for
> > now)
> >
> > *THANK YOU SO MUCH FOR THE INFORMATION AND THE HELP GUYS, 
> YOU ARE THE
> > BEST!!! REALLY!*
> >
> >
> > *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 2:37 PM Rowland penny via samba <
> > samba at lists.samba.org> wrote:
> >
> >> On 05/08/2019 13:27, L.P.H. van Belle via samba wrote:
> >> > I suggest, read :
> >> >
> >> 
> https://github.com/thctlo/samba4/blob/master/howtos/stretch-ba
> se-1.0.txt
> >> >
> >> 
> https://github.com/thctlo/samba4/blob/master/howtos/stretch-ba
> se-1.1-checkup.txt
> >> >
> >> 
> https://github.com/thctlo/samba4/blob/master/howtos/stretch-ba
> se-2.0-samba-minimal-ad.txt
> >> >
> >> 
> https://github.com/thctlo/samba4/blob/master/howtos/stretch-ba
> se-2.1-samba-minimal-ad-checks.txt
> >> >
> >> > Alsmost anything is in the samba wiki, execpt the debian install.
> >>
> >> Yes, the problem is that the Samba dns wikipages were 
> written from the
> >> Centos point of view and they need to have Debian info added.
> >>
> >>
> >> >
> >> > I suggest, start fresh, and follow above config. EXACLY, 
> why because i
> >> know that works.
> >> > Then when thats done, test it, and only then, your ready 
> to add new
> >> domains.
> >> > After you added one domain, then you can make changes so 
> you can setup
> >> views for bind.
> >> >
> >> I totally agree with starting anew with the AD dns, but I 
> still think
> >> that the DCs should only hold the AD dns info and forward 
> anything else
> >> to another DC.
> >>
> >> 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
> 
> 