It doesn't really matter. There are basically three options: foo.local dfg.ca.gov ad.dfg.ca.gov
The last two are my usual ones. The other thing I'll sometimes do is go use companyname.net for all internal stuff which I also like. Thanks, Brian Desmond [email protected] c - 312.731.3132 -----Original Message----- From: Joseph Heaton [mailto:[email protected]] Sent: Wednesday, April 28, 2010 9: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/> ~
