We have a public website at www.ourcompany.com, and everything was running smoothly until our development team deployed our Azure site to WordPress. Now, internal users are unable to access the public site, while external users have no issues. I discovered that on one of our domain controllers, IIS was configured with an HTTP redirect to www.ourcompany.com. Despite trying to adjust the headers and redirects, internal users continue to experience various errors based on my changes. I suspect this might be related to our domain being authoritative, but we can't reference the public space, so any request for ourcompany.com needs to hit an IIS server to leverage the CNAME record. Any thoughts on how to resolve this?
1 Answer
Instead of relying on redirects, try mirroring your public DNS setup on your internal DNS. If your public site has a straightforward A record, set up the same internally, pointing to the public IP. For a CNAME, do the same thing.
Are you suggesting pointing an internal domain to an external IP? That's a risky move for a sysadmin!