Personally I like to keep the internal and external domain names the same, it makes things easier for certificates.
This should be a pretty good all-in-one source for you. http://technet.microsoft.com/en-us/library/bb727085.aspx Thanks, Jeff Cain Technical Support Analyst Sunbelt Software Email: [email protected] Voice: 1-877-673-1153 Fax: 1-727-562-5199 Web: <http://www.sunbeltsoftware.com> Physical Address: 33 N Garden Ave Suite 1200 Clearwater, FL 33755 United States -------------------------------------------------------- If you do not want further email from us, please forward this message to [email protected] with the word 'unsubscribe' in the subject of your email. -------------------------------------------------------- Helpful Sunbelt Software Links: Knowledge Base Open a New Support Ticket Sunbelt Software Product Support Communities -----Original Message----- From: Joseph Heaton [mailto:[email protected]] Sent: Wednesday, April 28, 2010 10: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/> ~
