similar to: Samba generating wrong ipv6 and ipv4 address

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

samba generates an unknown ip4 and ip6 address. here is my settings: root at server:/# ifconfig enp1s0f2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.81.20 netmask 255.255.255.0 broadcast 192.168.81.255 inet6 fe80::21b:21ff:fea6:ce92 prefixlen 64 scopeid 0x20<link> inet6 2001:470:1f1b:5b5:21b:21ff:fea6:ce92 prefixlen 64 scopeid

On 03/08/2019 03:01, Patrik via samba wrote: > My config is this: > # Global parameters > [global] > # bind interfaces only = Yes > # if this is turned on, always perfect > # interfaces = lo 192.168.78.20 2001:470:1f1b:5b3:21b:21ff:fea6:ce93 > # interfaces = lo 192.168.78.20 2001:470:1f1b:5b3:21b:21ff:fea6:ce93 > 192.168.81.20 2001:470:1f1b:5b5:21b:21ff:fea6:ce92 > #

On 03/08/2019 11:17, Patrik wrote: > the problem is that dnsupdate is not working becuase i use dlz. i > cannot use dbsupdate with dnsupdate it fails. > *_ > _* What is 'dbsupdate' ? I can assure you that dnsupdate does work with dlz. I think you need to give us more info. Rowland

On 05/08/2019 09:55, Patrik via samba wrote: > the dig is wrong as well, it adds an additional ip address, which i have > not request to use other interfaces: > root at server:/# dig p3x-dc.patrikx3.com > Patrik, I have told you what your problem is, refusing to accept that you have setup Bind9 incorrectly is no reason for opening a new thread. Just in case you missed it, or

... From your output below.. >> Uncomment only single database line, depending on your BIND version << Then tell uss, why are 3 lines uncommented? I suggest, run : https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh Anonimize it where needed, and show me your server setup. Greetz, Louis > -----Oorspronkelijk bericht----- > Van:

My config is this: # Global parameters [global] # bind interfaces only = Yes # if this is turned on, always perfect # interfaces = lo 192.168.78.20 2001:470:1f1b:5b3:21b:21ff:fea6:ce93 # interfaces = lo 192.168.78.20 2001:470:1f1b:5b3:21b:21ff:fea6:ce93 192.168.81.20 2001:470:1f1b:5b5:21b:21ff:fea6:ce92 # interfaces = lo 192.168.81.20 2001:470:1f1b:5b5:21b:21ff:fea6:ce92 # if all interfaces

the dig is wrong as well, it adds an additional ip address, which i have not request to use other interfaces: root at server:/# dig p3x-dc.patrikx3.com ; <<>> DiG 9.11.5-P4-5.1-Debian <<>> p3x-dc.patrikx3.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11190 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0,

sorry i mean dnsupdate, if i use bind9 with samba dlz dnsupdate does not work, so i have to leave it out. my problem is that i got 2 interfaces and still it 2 dual stack ip addresses, the 192.168.78.0/24 is correct. the 192.168.81.0/24 is giving 192.168.81.120 instead of 192.168.81.20. i found the whole root since "/" with grep there is no 192.168.81.120 at all. only in my router there

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

the problem is that dnsupdate is not working becuase i use dlz. i cannot use dbsupdate with dnsupdate it fails. *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 Sat, Aug 3, 2019 at 9:22 AM Rowland penny via samba < samba at lists.samba.org>

but as i shown in my config i use bind9, why do you say i am using BIND9_FLATFILE DNS? root at server:/# cat etc/bind/named.conf.local // Consider adding the 1918 zones here, if they are not used in your // organization //include "/etc/bind/zones.rfc1918"; // the order is important!!!! first internal, then external!!! view "internal-enp1s0f3" { match-clients {

I am not using flatfiles and i using BIND_DLZ it shows in my log and i do not use flatfiles. BIND_DLZ only. as you can see it is pure bind and it just generates a weird ip address (192.168.81.120, 2001:470:1f1b:5b5:eeaa:a0ff:fe1b:4d84) this ip addresses cannot be pinged, missing this client. you can see in smb.conf i do not use dnsupdate either. and it is rotating and sometimes giving the wrong ip

the patrikx3.com is my domain my AD DC domain is p3x-dc.patrikx3.com, you can see: root at server:~# cat /etc/bind/zones/enp1s0f3/patrikx3.com ; Replaces on ennp1s0f2 to ennp1s0f3 ; 192.168.81. 192.168.78. ; 2001:470:1f1b:5b5:21b:21ff:fea6:ce92 2001:470:1f1b:5b3:21b:21ff:fea6:ce93 ; format is done with xed Linux Mint, not using tab, only space $TTL 3600 @

If i may. Rowland is right, below is not going to work as you want it to work. Bind9_flatfile with samba will be removed soon, because.. Its not supported. Read : https://wiki.samba.org/index.php/The_Samba_AD_DNS_Back_Ends Which states. Do not use the BIND9_FLATFILE DNS back end. It is not supported and will be removed in the future. And then this part. [router-logs] path =

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

I suggest, read : https://github.com/thctlo/samba4/blob/master/howtos/stretch-base-1.0.txt https://github.com/thctlo/samba4/blob/master/howtos/stretch-base-1.1-checkup.txt https://github.com/thctlo/samba4/blob/master/howtos/stretch-base-2.0-samba-minimal-ad.txt https://github.com/thctlo/samba4/blob/master/howtos/stretch-base-2.1-samba-minimal-ad-checks.txt Alsmost anything is in the samba

On 05/08/2019 12:50, L.P.H. van Belle via samba 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

On 05/08/2019 12:33, Patrik wrote: > the patrikx3.com <http://patrikx3.com> is my domain > my AD DC domain is p3x-dc.patrikx3.com <http://p3x-dc.patrikx3.com>, > you can see: > Unless you have done something strange like using 'p3x-dc' as the subdomain of 'patrikx3.com', that isn't your AD dns domain, it the FQDN of your AD DC. Rowland

This bug report is similar to this issue: https://www.dovecot.org/list/dovecot/2017-May/108116.html <https://www.dovecot.org/list/dovecot/2017-May/108116.html> I know it is not enough info, but every kill follows with this info: Feb 28 16:57:50 server dovecot[1511]: auth-worker: Fatal: master: service(auth-worker): child 17009 killed with signal 11 (core dumps disabled -