this post was submitted on 19 Dec 2023
8 points (100.0% liked)

homelab

6648 readers
21 users here now

founded 4 years ago
MODERATORS
 

Hello, wonderful people!

I am trying to set up two domains: a.domain.com and b.domain.com. The reason for having two domains is that one is for Active Directory, and the other is for the Linux domain using RHEL IDM.

The Windows server serves as the DHCP server, with the domain controllers' IP as the first DNS and the IDM controllers' IP as the second DNS. Both domains have a forward zone set up to point to the other domain, and this configuration seems to be working nicely so far.

Now, the issue: Let's say I have clients client.b.domain.com and client2.b.domain.com. They have successfully joined the IDM domain, but neither can ping each other's hostname nor perform an nslookup on it.

I also notice in the Windows DHCP server that the clients' FQDN is client.a.domain.com and client2.a.domain.com, even though I have set them to b.domain on the clients themselves.

Any ideas on how or what I need to change to get local hostnames working in this scenario?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] Concave1142@lemmy.world 1 points 11 months ago (1 children)

Not sure I fully understand the use of two domains. Does RHEL IDM do more for Linux machines compared to a Windows DC?

For my setup, I have a single Server 2019 AD Domain Controller that my Linux VM and laptop connect to using SSSD for domain level authentication.

[โ€“] kylian0087@lemmy.world 1 points 11 months ago* (last edited 11 months ago)

Yes RHEL IDM does. More linux specific like sudo rules for example.