Stefan G. Weichinger
2022-Nov-30 10:03 UTC
[Samba] accidentally upgraded DC to 4.17.3 ... didn't work
starting adc1 broke DNS for the windows clients, so I had to stop it again for now on adc1 I find: Nov 30 10:23:26 adc1 samba[80993]: /usr/sbin/samba_dnsupdate: ; TSIG error with server: tsig verify failure Nov 30 10:23:26 adc1 samba[80993]: [2022/11/30 10:23:26.255163, 0] ../../source4/dsdb/dns/dns_update.c:85(dnsupdate_n> Nov 30 10:23:26 adc1 samba[80993]: dnsupdate_nameupdate_done: Failed DNS update with exit code 41 I assumed that would be cleared after some initialization phase (like last week).
Rowland Penny
2022-Nov-30 10:19 UTC
[Samba] accidentally upgraded DC to 4.17.3 ... didn't work
On 30/11/2022 10:03, Stefan G. Weichinger via samba wrote:> > starting adc1 broke DNS for the windows clients, so I had to stop it > again for now > > on adc1 I find: > > Nov 30 10:23:26 adc1 samba[80993]:?? /usr/sbin/samba_dnsupdate: ; TSIG > error with server: tsig verify failure > Nov 30 10:23:26 adc1 samba[80993]: [2022/11/30 10:23:26.255163,? 0] > ../../source4/dsdb/dns/dns_update.c:85(dnsupdate_n> > Nov 30 10:23:26 adc1 samba[80993]:?? dnsupdate_nameupdate_done: Failed > DNS update with exit code 41 > > I assumed that would be cleared after some initialization phase (like > last week). > >Did the new DC's nameserver point to its own ipaddress before you started Samba ? You could try adding: dns update command = /usr/sbin/samba_dnsupdate --use-samba-tool to the DC's smb.conf and then restart Samba. Rowland