3

We host a domain on the internet that is accessible outside of our internal network using domain.com or www.domain.com, but is our actual internal network domain as well, but the external website is only accessible from our computers using www.domain.com - using domain.com gives "connection refused" in Chrome, and does a Bing search in IE.

I've asked our DNS guy about it, and he says internally domain.com goes to the internal network domain controller, and can't be rerouted/directed to the www version.

I've only done config on websites, not internal networks, so is there no way for domain.com from our internal network computers to resolve to www.domain.com?

Dave Heq
  • 35
  • 5
  • 1
    I agree with him, as AD places `A` records for the domain controllers at the apex of the domain. This conflicts with the assumption made by web browsers that the `A` records should point at a webserver. – Andrew B May 27 '16 at 16:27

1 Answers1

5

You've fallen victim to a bad decision made by whoever set up your AD environment internally. More discussion here.

Windows Active Directory naming best practices?

But the gist is that internally, your AD owns the name example.com in DNS. That name will always and forever (unless you rename the domain) point to your domain controllers. So the only way to redirect web requests to your actual web servers is to run a web server on every domain controller that is configured to do the redirect.

Community
  • 1
Ryan Bolger
  • 16,472
  • 3
  • 40
  • 59