I've taken over a network where both the internal and external domain names are identical, and now users can't access the website from within the office. I've added the external IP to the website's entry, but the web host is performing a 301 redirect that strips off 'www,' causing it to redirect to the domain controller instead. I'm looking for the easiest solution possible since I don't have access to the web host, and I'm hesitant to rename the Active Directory domain just yet.
1 Answer
While it's not ideal, one solution is to set up a small HTTPS proxy on your domain controllers that can redirect traffic to the actual IP of your website. You could also configure it so that 'www.domain.com' is the default, redirecting any direct traffic from 'domain.com' to the 'www' version. This has helped another customer in a similar situation and lets you create a 'www' DNS record for internal use.
But what if the web host is also doing redirects?