We have the following setup:
- Office 365 on mycompany.com
- AWS Route 53 as the DNS server for mycompany.com
- Azure as the hosting provider
I'm creating a new set of servers on Azure and I used Azure Active Directory Domain Services so that we can log into the servers using our Office 365 credentials.
mysite.mycompany.com is set up as a CNAME record on AWS to point to mysite.northeurope.cloudapp.azure.com and there is a public IP address set up with that name in Azure which points to a public load balancer which distributes the traffic between the two servers called mysite-web1.mycompany.com and mysite-web2.mycompany.com.
The problem is that I can't access the website mysite.mycompany.com from the Azure virtual network even though I can access it externally.
I assume that this is because the Azure virtual network just uses the Azure AD servers to get the domain name and doesn't go to AWS at all. There is no server on the Azure virtual network called mysite.mycompany.com
So I have a number of questions:
- Is there a way to make it work? I assume that I could just add the DNS name mysite.mycompany.com to AD DS but I'd rather not double maintain that info.
- Is this set up a bad idea? Assuming that I can fix it am I just going to run into other problems using the same name for the internal and external domains.