<div>
This is not a big problem and in fact MS states that its a good practice to name the internal domain name &nbsp;the same or similar to aid in integration. I agree with Neilsr that you simply need to add a record in your dns to point &quot;WWW&quot; to the correct external IP address. Of course if your websites IP address changes you will need to manually edit the www record. In your forward lookup zone simply add an &quot;A&quot; record type &quot;www&quot; and the IP and once you refresh your dns cache your internal devices will navigate to the website with no problems.<br />
<br />
MooseSupport
</div>


This is not a big problem and in fact MS states that its a good practice to name the internal domain name  the same or similar to aid in integration. I agree with Neilsr that you simply need to add a record in your dns to point "WWW" to the correct external IP address. Of course if your websites IP address changes you will need to manually edit the www record. In your forward lookup zone simply add an "A" record type "www" and the IP and once you refresh your dns cache your internal devices will navigate to the website with no problems.

MooseSupport

<div>
I will be visiting the client in 3 weeks and will attempt this. &nbsp;Thanks for the suggestion.
</div>


I will be visiting the client in 3 weeks and will attempt this.  Thanks for the suggestion.

<div>
Thanks so much will look into that when I visit the client in 3 weeks
</div>


Thanks so much will look into that when I visit the client in 3 weeks

<div>
<div class="content wysiwyg-content">
I inadvertently created a local domain controller for a client using windows server 2012 R2 with the same name as her web domain. &nbsp;Now, nobody can access the web page from the office. &nbsp;I understand I can modify the host file on the workstations to get around this. &nbsp;All the workstations (17) are Windows 7 Pro SP1. &nbsp;What information do I need to do this. &nbsp;Any step by step guide would really be appreciated.
</div>
</div>


I inadvertently created a local domain controller for a client using windows server 2012 R2 with the same name as her web domain.  Now, nobody can access the web page from the office.  I understand I can modify the host file on the workstations to get around this.  All the workstations (17) are Windows 7 Pro SP1.  What information do I need to do this.  Any step by step guide would really be appreciated.

domain controller and website the same

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

A web server refers to the software that helps to deliver web content that can be accessed either through the Internet or through an intranet. The primary function of a web server is to store, process and deliver web pages to clients. The communication between client and server takes place using the Hypertext Transfer Protocol (HTTP). The most common use of web servers is to host websites, but there are other uses such as gaming, data storage, running enterprise applications, handling email, FTP, etc.