[Samba] samba_dnsupdate

[L.P.H. van Belle]

Ah the ipv6 :  2002:8282:00ca:0000:0000:0000:8282:00ca 
The corresponding IPv4 address is 130.130.0.202 

Does that ring a bel? 


> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Paul 
> Littlefield via samba
> Verzonden: maandag 2 maart 2020 16:04
> Aan: samba at lists.samba.org
> Onderwerp: Re: [Samba] samba_dnsupdate
> 
> On 02/03/2020 14:16, Rowland penny via samba wrote:
> > You could try commenting out the line in dns_update_list.
> 
> OK.
> 
> > Write another script that does nothing and use that instead 
> (just for testing) ?
> 
> OK, or add and change this line to remove the 'dnsupdate' service?
> 
> server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, 
> drepl, winbindd, ntp_signd, kcc, dnsupdate, dns
> 
> 
> > Yes, this is what I did when testing Ubuntu 18.04, but 
> perhaps Louis has further comments ?
> 
> Noted.
> 
> > It looks like it is trying to update its own dns records 
> and if you are using dhcp to update the records in AD they 
> shouldn't be.
> 
> I'm not using DHCP to update DNS... I don't use BIND.
> 
> The plot thickens... the lease is set for 6 hours and should 
> a Windows Server be trying to update anything to do with a 
> Samba 4 AD DC?!
> 
> Just to clarify, so far it's just 4 Windows Servers that are 
> ADDING their IPv6 addresses.
> 
> **UPDATE**
> 
> It's just happened again, so I have logged in to the Windows 
> Server and checked it's IPv6 address which bears NO 
> resemblance to the entry in the Samba 4 DNS...
> 
>    Name=V-INT, Records=2, Children=0
>      AAAA: 2002:8282:00ca:0000:0000:0000:8282:00ca (flags=f0, 
> serial=110, ttl=1200)
>      A: 130.130.0.202 (flags=f0, serial=934, ttl=900)
> 
> actual IPv^ address = 'fe80::7c57:b0d5:d6b9:ecc%12'
> 
> 
> Help!
> 
> Regards,
> 
> Paully
> 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
> 
>