RE: Windows 2003 Active Directory

  • From: Dan HINCKLEY <danslists@xxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Mon, 07 Mar 2005 13:18:24 +0100

At 12:53 3/7/2005, you wrote:

This actually works and solves one problem. If you dont name your AD domain to the name of actual domain name, then at times, machines go out to look for that domain unless you have your domain ending with .local., in a NATing scenario.

In this scenario, you need to maintain separate servers for internal and external.


Chand 

Chand,

Can you point me to a URL with documentation on .local?


----------
From: Steve Moffat [mailto:steve@xxxxxxxxxx]
Sent: Monday, March 07, 2005 5:15 PM
To: [ExchangeList]
Subject: [exchangelist] RE: Windows 2003 Active Directory

Absolutely


----------
From: rahil [mailto:rahil.warang@xxxxxxxxx]
Sent: Monday, March 07, 2005 7:41 AM
To: [ExchangeList]
Subject: [exchangelist] RE: Windows 2003 Active Directory

Dear Steve,
Are you sure on this

-----Original Message-----
From: Steve Moffat [mailto:steve@xxxxxxxxxx]
Sent: Monday, March 07, 2005 3:28 PM
To: [ExchangeList]
Subject: [exchangelist] RE: Windows 2003 Active Directory

You will have no problems using a .com for your internal domain.



Other related posts:

  1. Home
  2. exchangelist
  3. Archive
  4. 03-2005