I have a website named contoso.com registered with go-daddy. In go daddy, I set the name servers to hostgator name servers, so Hostgator hosts the contoso.com website and has the dns records for the site.
On premise, I have a domain named contoso.com, same as the website.
Microsoft Azure allows you to create your custom domain name instead of using the generic "<email>onmicrosoft.com." I decided to create a custom AzureAD domain of contoso.com.
Before you can get this custom domain set up, Microsoft issues a challenge for you to create a txt or mx record in the contoso.com zone to prove you own it. After doing this, your custom domain is verified and you are able to use contoso.com.
On premise, when using Azure ADConnect, I am able to sync all users in my on premise contoso.com domain to my AzureAD contoso.com domain. However, when I try to resolve the contoso.com website from a computer in the on premise contoso.com domain, I am unable
do do so. It says, "this site can't be reached."
To try and fix this, I created an A record named www that points to contos.com website IP. This also fails. I then renamed the onprem domain to contoso.local. After doing this, I was now able to get to the website from a computer in the newly renamed contoso.local
domain but now when I try to sync users to AzureAD, they show up as "user@<email>onmicrosoft.com" instead of "user@contoso.com.
How can I keep my local domain as contoso.com, which allows me to properly sync names to AzureAD, and at the same time, be able to get to the website from clients within the contoso.com on-premise domain?
↧
AD Connect Sync issues
↧