- 新しい順
- 投票が多い順
- コメントが多い順
Hello! If I understand you correctly, you have this scenario:
- You have two directories, let's call it a.local and b.local.
- You need computers joined to a.local to resolve hostnames in b.local and viceversa.
Operating systems use the concept of DNS suffixes (Windows) or DNS search order (UNIX-like OS). This is what allows a computer to request the dns of "server" and it is automatically converted to a FQDN using a suffix (i.e a.local). So when querying "server", the OS is actually querying server.a.local. You can check this behavior with any packet capture software. You can add several suffixes. For example, in Windows you can do this in the network interface adapter.
So, in order to get this working, you need two things:
- Add the new suffixes to your clients (machines)
- Ensure that both DNS servers (i.e domain controllers) can resolve each other's resources.
For 2), this depends on the DNS IP addresses you are using:
- If you are using the domain controllers IP addresses, you need to add conditional forwarders [1].
- If you are using Route 53, you need to create outbound DNS resolvers [2]. I suggest to read this AWS blog [3] for a deeper understanding of how to integrate DNS between AD and Route 53.
Have a great day ahead!
[1] https://woshub.com/dns-conditional-forwarding-policy-windows-server/ [2] https://repost.aws/knowledge-center/route53-resolve-with-outbound-endpoint [3] https://aws.amazon.com/blogs/networking-and-content-delivery/integrating-your-directory-services-dns-resolution-with-amazon-route-53-resolvers/
関連するコンテンツ
- AWS公式更新しました 2年前