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
Stefan G. Weichinger
2019-Jul-31 10:40 UTC
[Samba] GPO issues - getting SYSVOL cleaned up again
Am 31.07.19 um 12:32 schrieb Rowland penny via samba:> On 31/07/2019 11:22, Stefan G. Weichinger via samba wrote: >> "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.definitely, see the rgrep ;-)
On 31/07/2019 11:40, Stefan G. Weichinger via samba wrote:> Am 31.07.19 um 12:32 schrieb Rowland penny via samba: >> On 31/07/2019 11:22, Stefan G. Weichinger via samba wrote: >>> "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. > definitely, see the rgrep ;-) >Rename the cache file '/var/lib/samba/private/dns_update_cache', stop then restart Samba, this should cause the cache to be recreated, hopefully without 'dc' ;-) Rowland
L.P.H. van Belle
2019-Jul-31 10:56 UTC
[Samba] GPO issues - getting SYSVOL cleaned up again
Hai, I just renamed that file to .old on one of my DC's. systemctl stop samba-ad-dc && systemctl start samba-ad-dc New file is created yes, so this looks like the solution. Stefan, once this is done. Verify again the servers in : Sites - Default-First-Site-Name - Servers Windows DNS tool, zone your.dom.tld. For the A IN-ARPA .. For the PTR. _msdcs.your.dom.tld. For GUIDs. If its all good now, give it a few min, then verify the samba ad replication again. Greetz, Louis> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland penny via samba > Verzonden: woensdag 31 juli 2019 12:50 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] GPO issues - getting SYSVOL cleaned up again > > On 31/07/2019 11:40, Stefan G. Weichinger via samba wrote: > > Am 31.07.19 um 12:32 schrieb Rowland penny via samba: > >> On 31/07/2019 11:22, Stefan G. Weichinger via samba wrote: > >>> "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. > > definitely, see the rgrep ;-) > > > Rename the cache file '/var/lib/samba/private/dns_update_cache', stop > then restart Samba, this should cause the cache to be recreated, > hopefully without 'dc' ;-) > > Rowland > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: lists.samba.org/mailman/options/samba > >