search for: addomaincontroller

...nced_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?

...ith 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 w...

...ause '.local' is reserved for mdns. I am aware of the .local domain. However, my implementation is over 15 years old, and back then, some guides recommended it. Changing it now is very difficult. > >> 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 ? # samba-tool computer show DC2022 --attributes=name,dNSHostName dn: CN=DC2022,OU=Domain Controllers,DC=wenus...