RE: Regarding non-standard TLDs

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Allen Firouz (AllenFirouz_at_discussions.microsoft.com)
Date: 01/22/05 

Date: Fri, 21 Jan 2005 19:05:02 -0800

Bob,

I seem to say this waaay too often, but, don't structure your network on
what your neighbor is doing. Let business needs drive your systems design.
Whatever works best for your company, use Best Practices to get there. I am
a proponent of two separate domain names, but again, that is a business
decision. To rename, use the Domain Renaming Tool. Not as hairy as you
think, actually.

good luck,

-Allen Firouz

"Bob Williamson" wrote:

> Yeah, the domain rename process was one of my justifications for moving to
> 2003 AD, but it sure sounds like a hairy project. I have 65 users, 13
> servers and two locations.
>
> The problem with doing any of this is it must be done WITHOUT interrupting
> peoples work.
>
> Interesting note: I had a conversation with PSS a couple months back. They
> stated they PREFER .local for security reasons. Also, look in the install
> manual of SBS 2003, they state to use .local.
>
> Thanks you for your opinions,
> Bob
>
> "Allen Firouz" wrote:
>
> > Bob,
> >
> > If you are using Windows 2003, it has become fairly easy to change your
> > domain name. You can use the Domain Renaming Tool
> > (http://www.microsoft.com/windowsserver2003/downloads/domainrename.mspx) .
> > Remember that there are ramifications for changing the domain name and it can
> > affect your group polcies and Exchange (if you use Exchange). Use this link
> > for some caveats:
> > http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/deployguide/en-us/dmebb_gpu_nnvg.asp
> >
> > Good luck,
> >
> > -Allen Firouz
> >
> > "Bob Williamson" wrote:
> >
> > > Way back when, the standard line was to use a nonstandard TLD for internal
> > > networks (as opposed to a split DNS config). Since that time things have
> > > changed, more laptops, more integration between the internet and internal
> > > network (RPC over HTTP etc).
> > >
> > > So I am currently running company.com on the internet wioth DNS handled by
> > > my ISP and company.local internally.
> > >
> > > I keep wanting to change this to .com, not the easiest task, and am
> > > hesitating on implementign some new projects thinking I already have a deep
> > > enough .local hole.
> > >
> > > So my question is How bad off am I with the .local?
> > > What is the SOP for namign internal domains now?
> > > Should I seriously think about changing it or am I ok long term?
> > >
> > > etc.
> > >
> > > Thanks,
> > > Bob
> > >
> > > PS When I started this job the NT 4.0 domain was named with an "&" in it.
> > > This caused all kinds of issues when I moved to W2K. I am concerned that
> > > long term the .local might cause a similar problem.
> > >