RE: Windows 2003 Active Directory

  • From: "adrian bolzan" <abolzan@xxxxxxxxxxxxxxxxxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 8 Mar 2005 09:52:04 +1100



> -----Original Message-----
> From: John Tolmachoff (Lists) [mailto:johnlist@xxxxxxxxxxxxxxxxxxx]
> Sent: Monday, 7 March 2005 7:07 PM
> To: [ExchangeList]
> Subject: [exchangelist] RE: Windows 2003 Active Directory
>
> http://www.MSExchange.org/
>
> > >From my own experience I would say that you should not use your
> > >public
> > domain name as your internal AD domain name; I would recommend
> > something like "kenya-airways.local".  As you host your website
> > externally, and I presume use external DNS servers, you
> will find that
> > you will not have to manage your Windows DNS servers as much.
>
> DO NOT USE ".local" AS THE TLD.
>
> That is not a valid private use TLD:
>
> http://www.windowsitpro.com/Article/ArticleID/44818/44818.html
>


Thanks, John, for pointing this out to me- I had not even thought of it.
I see that Microsoft use .msft in their presentations.  Anyone know what
the "ft" part stands for?

When I upgraded to AD from NDS I did not really understand the
ramifications of using one of my public domain names as our AD domain
name, nor did the service integrator I engaged.  Nor did they realise
that exchange should not be installed on a DC.  As such I am now
planning a domain rename, as well as demoting the DC with exchange to a
member server,

Trhanks,
Adrian

============================================================
IMPORTANT - This email and any attachments is confidential.
If received in error, please contact the sender and delete
all copies of this email. Please note that any use,
dissemination, further distribution or reproduction of this
message in any form is strictly prohibited. Before opening or
using attachments, check them for viruses and defects.
Regardless of any loss, damage or consequence, whether caused
by the negligence of the sender or not, resulting directly or
indirectly from the use of any attached files, our liability
is limited to resupplying any affected attachments. 
Any representations or opinions expressed in this email are
those of the individual sender, and not necessarily those
of the Capital Transport Group.
============================================================


Other related posts: