samba - Dec 2024 - Problem after join Windows Serwer 2022 DC to Samba AD

I am testing the addition of a Windows Server 2022 DC to an AD based on 
a Samba DC according to 
https://samba.tranquil.it/doc/en/samba_advanced_methods/samba_add_windows_active_directory.html#samba-add-windows-active-directory
. It seems to be added to the domain correctly. When I check with the 
command: nslookup -type=SRV _ldap._tcp.wenus.local, it shows all DCs, 
including the new one. However, when I query using the command: 
Get-ADDomainController -Filter * | Select-Object Name, HostName, I don?t 
see the new controller.

I also noticed that the SPN DNS/dc2022.wenus.local for the new DC hasn?t 
been created.

I checked the replication, and it doesn?t show any errors.

Do you have any idea what might be the cause?

On Fri, 20 Dec 2024 12:18:45 +0100
Programnet via samba <samba at lists.samba.org> wrote:
> I am testing the addition of a Windows Server 2022 DC to an AD based
> on a Samba DC according to 
>
https://samba.tranquil.it/doc/en/samba_advanced_methods/samba_add_windows_active_directory.html#samba-add-windows-active-directory
What version of Samba are you using and on what OS ?
Have you raised the functional level to 2016 ?
> . It seems to be added to the domain correctly. When I check with the 
> command: nslookup -type=SRV _ldap._tcp.wenus.local, it shows all DCs, 
Please do not use '.local' as a TLD, not even in sanitisation, it is
confusing because '.local' is reserved for mdns.
> including the new one. However, when I query using the command: 
> Get-ADDomainController -Filter * | Select-Object Name, HostName, I
> don?t see the new controller.
What does 'samba-tool computer show $DC_HOSTNAME
--attributes=name,dNSHostName' display ?
> 
> I also noticed that the SPN DNS/dc2022.wenus.local for the new DC
> hasn?t been created.
I wouldn't worry about that. none of my DCs have that SPN

Rowland