On 31/07/2019 11:02, Stefan G. Weichinger via samba wrote:> Am 31.07.19 um 11:58 schrieb L.P.H. van Belle via samba: >> Restarted or stop-start, because there is a difference between these. >> You MUST use stop/start > I read "restart" and did "systemctl restart" ;-) > > stop/start now on both > > no change > > But a trace of the problematic name: > > task[dnsupdate][25128]: /usr/sbin/samba_dnsupdate: couldn't get > address for 'dc.mydomain.at': not found >I take it that 'dc.mydomain.at' is the FQDN of the DC you stopped then started, if so, it looks like the DC does not know its own record. What does 'host -t A dc.mydomain.at' return ? Rowland
Stefan G. Weichinger
2019-Jul-31 10:22 UTC
[Samba] GPO issues - getting SYSVOL cleaned up again
Am 31.07.19 um 12:17 schrieb Rowland penny via samba:> On 31/07/2019 11:02, Stefan G. Weichinger via samba wrote: >> Am 31.07.19 um 11:58 schrieb L.P.H. van Belle via samba: >>> Restarted or stop-start, because there is a difference between these. >>> You MUST use stop/start >> I read "restart" and did "systemctl restart" ;-) >> >> stop/start now on both >> >> no change >> >> But a trace of the problematic name: >> >> task[dnsupdate][25128]:?? /usr/sbin/samba_dnsupdate: couldn't get >> address for 'dc.mydomain.at': not found >> > I take it that 'dc.mydomain.at' is the FQDN of the DC you stopped then > started, if so, it looks like the DC does not know its own record. What > does 'host -t A dc.mydomain.at' return ?"dc" was the old name a few years ago I try to get rid of that now. host -t A dc... not found. We want that in the end.
On 31/07/2019 11:22, Stefan G. Weichinger via samba wrote:> Am 31.07.19 um 12:17 schrieb Rowland penny via samba: >> On 31/07/2019 11:02, Stefan G. Weichinger via samba wrote: >>> Am 31.07.19 um 11:58 schrieb L.P.H. van Belle via samba: >>>> Restarted or stop-start, because there is a difference between these. >>>> You MUST use stop/start >>> I read "restart" and did "systemctl restart" ;-) >>> >>> stop/start now on both >>> >>> no change >>> >>> But a trace of the problematic name: >>> >>> task[dnsupdate][25128]:?? /usr/sbin/samba_dnsupdate: couldn't get >>> address for 'dc.mydomain.at': not found >>> >> I take it that 'dc.mydomain.at' is the FQDN of the DC you stopped then >> started, if so, it looks like the DC does not know its own record. What >> does 'host -t A dc.mydomain.at' return ? > "dc" was the old name a few years ago > > I try to get rid of that now. > > host -t A dc... not found. We want that in the end. > >Ah, my mistake. The samba_dnsupdate script uses a file 'dns_update_list to check for records and create any missing ones, this uses '${HOSTNAME}', so it looks like somewhere 'dc' still exists. Rowland