[Samba] Samba crashes and won't restart

[Allen Chen]

Hi Rowland,

Is there any reason for a DC must to use its self as its first 
nameserver? Can you point me to a link regarding this requirement on 
samba website?

Thanks,

Allen

On 6/21/2022 8:18 AM, Rowland Penny via samba wrote:
> On Tue, 2022-06-21 at 13:51 +0200, Alexander Harm || ApfelQ via samba
> wrote:
>> Thanks for your reply.
>>
>> I indeed run Louis’ packages on Debian Bullseye. We have 4 instances
>> in 3 locations. Apart from one they run in a Proxmox VM. The ones
>> showing this behaviour are both in location A, one VM on Proxmox, one
>> VM on Synology (both are KVM). The other sites, running the same
>> version do not show any of this behaviour.
>>
>> Here the requested output:
>>
>> Config collected --- 2022-06-21-13:43 -----------
>>
>> Hostname: ka-h9-dc01
>> DNS Domain: ds.example.com
>> Realm: DS.EXAMPLE.COM
>> FQDN: ka-h9-dc01.ds.example.com
>> ipaddress: 10.0.1.250
>>
>> -----------
>>
>> This computer is running Debian 11.3 x86_64
>>
>> -----------
>>
>> running command : ip a
>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>> group default qlen 1000
>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> inet 127.0.0.1/8 scope host lo
>> inet6 ::1/128 scope host
>> 2: ens18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
>> state UP group default qlen 1000
>> link/ether 22:2a:f3:8f:21:8f brd ff:ff:ff:ff:ff:ff
>> altname enp0s18
>> inet 10.0.1.250/24 brd 10.0.1.255 scope global noprefixroute ens18
>> inet6 fe80::3b1d:5481:53e6:72c6/64 scope link noprefixroute
>>
>> -----------
>>
>> Checking file: /etc/hosts
>>
>> 127.0.0.1 localhost
>> 10.0.1.250 ka-h9-dc01.ds.example.com ka-h9-dc01
>>
>> # The following lines are desirable for IPv6 capable hosts
>> ::1 localhost ip6-localhost ip6-loopback
>> ff02::1 ip6-allnodes
>> ff02::2 ip6-allrouters
>>
>> -----------
>>
>> Checking file: /etc/resolv.conf
>>
>> # Generated by NetworkManager
>> search ds.example.com
>> nameserver 10.88.80.88
>> nameserver 10.0.1.250
> Your nameservers are the wrong way around, a DC must use itself as its
> first nameserver.
>> -----------
>>
>> 'kinit Administrator' password checked failed.
>> Wrong password or kerberos REALM problems.
>>
> Which will probably explain the above.
>
> Rowland
>
>
>