Sep 29 2020 05:48 PM
Hi,
i have to make sure the requirement,
I have two forest and want to deploy Exchange hybrid with single tenant. based on this article https://docs.microsoft.com/en-us/exchange/hybrid-deployment/hybrid-with-multiple-forests,
there is no requirement to configure forest trust to deploy Exchange hybrid
is it correct we can do without trust ?
how azure AD Connect recognize the other domain without trust ?
thanks
Oct 02 2020 02:09 PM
Oct 07 2020 07:34 PM
Hi, @SeanMcAvinue
happy to hear there is no trust required
if I already make azure ad connect and other forest dc ping each other, is there any other requirement like conditional dns forwarder ? because not all the resource/ip address is routable each domain. I just need to run sync user only.
Thanks for your reply
Oct 08 2020 12:54 AM
Oct 08 2020 01:39 AM
I already test with conditional forwarders, but conditional forwarders is not suitable with my environment.
lets give me example, i have two forest. contoso.com and fabrikam.com
If i enable conditional forwarder fabrikam.com in contoso DNS, all record to fabrikam.com will route trough dns A record. if contoso client try to ping www.fabrikam.com, it will resolve by internal ip, and the routing is not availble, the result is ping www.fabrikam.com is RTO. My requirement is when contoso client ping www.fabrikam.com, it will resolve by ip public
i curious, is it any solution that suit to my requirement ? is it hostfile available to do that ?
Thanks before
Oct 08 2020 03:48 AM
SolutionHost file records should work but generally not recommended as they introduce complexity and manual configuration. Alternatively you could look at a dedicated non-AD integrated DNS server to manage just the AD Connect lookups, or update your public records in your internal DNS servers to point to public IP (This depends on if that will impact your internal users..
Oct 08 2020 03:48 AM
SolutionHost file records should work but generally not recommended as they introduce complexity and manual configuration. Alternatively you could look at a dedicated non-AD integrated DNS server to manage just the AD Connect lookups, or update your public records in your internal DNS servers to point to public IP (This depends on if that will impact your internal users..