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

@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...

Regards
Ingo
https://github.com/WAdama

'Ingo Asche' via samba schrieb am 07.12.2022 um
22:24:
> Hi Roy,
>
> I'm afraid not.
>
> My systems are all 64bit. And I'm already on 2:4.17.3 at dfsg-3.
>
> Regards
>
> Ingo
> https://github.com/WAdama
>
> spindles seven via samba schrieb am 07.12.2022 um 20:09:
>> On? 07 December 2022 14:25 Ingo Asche wrote:
>>> And this happened first after updating Samba 4.16.6 to Samba 4.17.3
>>> via Debian
>>> backports.
>>>
>> Is your OS a 32-bit version??? If so Michael updated Debian Backports 
>> with a fix for 32-bit systems
>> using version 4.17.3.? If you have version 2:4.17.3_dfsg-1 it has the 
>> bug you describe for 32-bit systems.
>> Look to update to version 2:4.17.3+dfsg-2 or 2:4.17.3 at dfsg-3 to fix 
>> this.
>>
>> HTH
>>
>> Roy
>>
>>
>
>

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