Domain name question

**Iphone** · 13-Apr-2007, 06:08 AM

Question: We are attemtping to install a new Windows Server 2003 machine which will function as a Domain Controller, Exchange Server, and IIS server. Currently the client is running a NAME.local domain and they are NOT running their own email server -- with this new server we will be setting up Exchange and IIS to handle all mail and web traffic internally, so my question is this: is there any advantage/disadvantage to making the local domain name NAME.com instead of NAME.local? I.e., do we need to match the network's internal domain name match that of the publicly accessible domain name?

**Iphone** · 13-Apr-2007, 06:08 AM

no....you don't need to match the network internal domain name with the public domain name. In fact, it is recommended that you do not do this.

13-Apr-2007, 06:08 AM	#1 (permalink)
Iphone Fixed Error! Posts: 4,202 Join Date: Mar 2007 Rep Power: 6 IM:	Domain name question Question: We are attemtping to install a new Windows Server 2003 machine which will function as a Domain Controller, Exchange Server, and IIS server. Currently the client is running a NAME.local domain and they are NOT running their own email server -- with this new server we will be setting up Exchange and IIS to handle all mail and web traffic internally, so my question is this: is there any advantage/disadvantage to making the local domain name NAME.com instead of NAME.local? I.e., do we need to match the network's internal domain name match that of the publicly accessible domain name?

13-Apr-2007, 06:08 AM	#2 (permalink)
Iphone Fixed Error! Posts: 4,202 Join Date: Mar 2007 Rep Power: 6 IM:	Re: Domain name question no....you don't need to match the network internal domain name with the public domain name. In fact, it is recommended that you do not do this.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)