Tell your Novell guy you want to name it "workgroup" and see what he does.
-----Original Message----- From: Charlie Kaiser [mailto:[email protected]] Sent: Wednesday, April 28, 2010 9:28 AM To: NT System Admin Issues Subject: RE: Current AD domain naming best practices Personally, I always go for a different internal name if for no other reason than to simplify DNS. Using domain.com on the outside and domain.local (or something) on the inside avoids unforeseen headaches (like DNS name clashes) down the road. Among other things... *********************** Charlie Kaiser [email protected] Kingman, AZ *********************** > -----Original Message----- > From: Joseph Heaton [mailto:[email protected]] > Sent: Wednesday, April 28, 2010 7:22 AM > To: NT System Admin Issues > Subject: Current AD domain naming best practices > > We are currently in the beginning phases of migrating from Novell > e-Directory, to AD. We are having discussions to decide on a new > internal domain name. I know that years ago, it was best practice to > have a different internal domain name from your external domain name, > which is what the Novell guy is holding onto, like a pitbull to a > mailman's leg. Is that still true today? We are on private IPs > internally, so external forces can't route to the inside anyway, so my > thinking, and the other Windows admins, is that having the same FQDN > internally would be ok. > > TIA, > > Joe > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ > <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
