[Samba] File server joined to a samba domain accessed by windows 10-11 clients, works via ip no via dns name

[Ingo Asche]

I'm totally with you...

Especially because an older NAS is still working.

As I wrote before a support ticket in my case is already opened. I tried 
to deliver the necessary data and am now waiting. Maybe Travis will open 
also one to show them it is not a single case.

By the way, the new version of their Samba service will be much nearer 
to the actual Samba than now: 4.15.9, old but at least not EOL...

Regards
Ingo
https://github.com/WAdama

Rowland Penny via samba schrieb am 08.12.2022 um 10:45:
>
>
> On 08/12/2022 09:22, Ingo Asche via samba wrote:
>> @Rowland:
>>
>> Just to be on the sure side I have checked DNS for the kerberos and 
>> ldap entries from NAS side.
>>
>> nslookup -type=any _kerberos._udp.service.mydomain.de
>> Server:         192.168.181.80
>> Address:        192.168.181.80#53
>>
>> _kerberos._udp.service.mydomain.de      service = 0 100 88 
>> dc1.service.mydomain.de.
>> _kerberos._udp.service.mydomain.de      service = 0 100 88 
>> dc0.service.mydomain.de.
>> _kerberos._udp.service.mydomain.de      service = 0 100 88 
>> dc2.service.mydomain.de.
>>
>> nslookup -type=any _ldap._tcp.service.mydomain.de
>> Server:         192.168.181.80
>> Address:        192.168.181.80#53
>>
>> _ldap._tcp.service.mydomain.de  service = 0 100 389 
>> dc0.service.mydomain.de.
>> _ldap._tcp.service.mydomain.de  service = 0 100 389 
>> dc2.service.mydomain.de.
>> _ldap._tcp.service.mydomain.de  service = 0 100 389 
>> dc1.service.mydomain.de.
>>
>> (I have to use nslookup, host command doesn't exist on Synology NAS)
>>
>> So I'm pretty sure DNS still works...
>>
>
> Then the finger seems to be pointing firmly at synology, everything 
> works correctly for myself on Samba 4.17.3
>
> Rowland
>
>