Matt Mossholder on 20 Apr 2010 06:52:38 -0700 |
On Tue, Apr 20, 2010 at 9:31 AM, Mike Leone <turgon@mike-leone.com> wrote: > > Renaming an AD domain is a scary and fragile undertaking, and not to be > done lightly, I am told (we're thinking of renaming our work domain, > though not for this reason). If we did rename it, we'd probably follow > the recommended best practices, which is to use something like ".local" ... > > Anyway, I will try it tonight, when I get home ... > A sensible compromise that I have seen other companies use is to take their xyzpdq.com, and remove the .com ... so the internal domain is .xyzpdq , and the public domain is xyzpdq.com. Another one I have seen is .internal . Like I said, .local is already taken, and leads to problems like this one :) -- --Matt ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|