[Samba] accidentally upgraded DC to 4.17.3 ... didn't work
rpenny at samba.org
Wed Nov 30 11:37:37 UTC 2022
On 30/11/2022 10:58, Stefan G. Weichinger via samba wrote:
>> Did the new DC's nameserver point to its own ipaddress before you
>> started Samba ?
> adc1 has the IP 10.0.0.231 on interface "eno1"
> the resolv.conf contains its own IP at first and 10.0.0.230 for "adc2"
> at second ->
> # resolv.conf
> nameserver 10.0.0.231
> nameserver 10.0.0.230
> search arbeitsgruppe.my.tld
> both DCs have several VLAN-interfaces and IPs as well
> on adc2 I have
> bind interfaces only = yes
> interfaces = lo enp0s31f6
> while on adc1 these lines are currently missing -> smb.conf was created
> from scratch at the join
> Last week there were numerous DNS-records added: one per VLAN ... maybe
> that is a problem, I removed them last week to run the DC in plain
> VLAN1= LAN only.
What are the VLANs for and what do they have to do with the DC ?
> I assume I should add that binding-config to adc1 as well.
>> You could try adding:
>> dns update command = /usr/sbin/samba_dnsupdate --use-samba-tool
>> to the DC's smb.conf and then restart Samba.
> Can do, have to check with the customer first: breaking the DNS as
> before isn't good while people are working.
The samba_dnsupdate python script is run by a DC at startup and then
every 10 minutes, it adds any missing AD dns records and there are quite
a few missing from a newly joined DC. You can see the records that are
There can be a problem with the ticket, but, by using samba-tool, this
can be got around.
More information about the samba