This question already has an answer here:
I have an intranet network on which a Windows IIS7 server is named mycompany.com. We also have a website hosted elsewhere named mycompagny.com.
From the outsite of the network, everything is fine for our current use case. But from the inside, it's not possible to access the website in a browser without the www prefix. It return a dummy page from IIS7.
A hack used by a colleague is to skip local DNS routing by using google's DNS service. A major con for the solution is that it have to be configured locally on all machines and that it disable local http serving.
Another hack would be to always use www, but we have some subdomains that are not configured to work with it. For example, our famous: nice-app.mycompagny.com.
I can't just change the intranet server name because it's already used for other purpose as ssh-access-ing a bunch of machines ftp-serving. Renaming mycompagny.com by mycompagny-intranet.com or something else would certainly breaks a lot of things and create headheaches for everyone for a couple of days ... As I am new here, I can't afford it.
How could I handle that specific problem?
This kind of duplicate use of DNS duplicate seem to be a common anti-pattern in the windows server community, at least it have been reported many times on Serverfault:
- website/email server
- DNS Active Directory / website
- intranet / external world
- and many other sauces...
How could one prevent that to happen again at the design stage of a network?
EDIT: The sub-question is clearly a duplicate of Windows Active Directory naming best practices?.