question

g-orwell avatar image
0 Votes"
g-orwell asked LimitlessTechnology-2700 edited

Connect on premise AD with private DNS name to the SaaS feature Forticlient EMS

Hi all,



I need to connect my forticlient EMS cloud with my Active Directory on premise.

But my active directory on premise use a private DNS domain name.

I want use haproxy as ADFS proxy instead of Windows proxy and two ADFS Windows 2019 server but I have some questions about how to make all of this work with an public DNS name (to point on ADFS proxy EndPoint ) and my ADFS connected to my pirvate on premise AD that use private domain name).



Is this will work if I put an public DNS name that point to haproxy-adfs proxy and if haproxy ADFS backend point to ADFS pool of on premise AD with private DNS name.

My Forticlient EMS cloud ask for the following information.

129255-fortiems.jpg




Thank you for your response

windows-active-directoryadfswindows-dhcp-dns
fortiems.jpg (44.0 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

LimitlessTechnology-2700 avatar image
0 Votes"
LimitlessTechnology-2700 answered LimitlessTechnology-2700 edited

Hi there,

It seems you must use a DNS forwarder in Azure, which in turn is responsible for resolving all the DNS queries.
Depending on how you use Azure to host IaaS, PaaS, and hybrid solutions, you might need to allow the virtual machines (VMs), and other resources deployed in a virtual network to communicate with each other
https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances

Hope this Answers all your queries , if not please do repost back .
If an Answer is helpful, please click "Accept Answer" and upvote it : )

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.