I'm simply gathering information on the 3 options, and what everyone recommends. Unfortunately, there is no clear-cut "winner". I've found that all 3 are valid options, depending on how much administrative overhead you want to add to the process. However, Michael Smith brought up a rather strong concern over why different names would be bad, if you're possibly going to implement ADFS.
Anyway, I very much appreciate your, and everyone's, input. Joe >>> "Andrew S. Baker" <[email protected]> 4/28/2010 12:33 PM >>> A subdomain is fine, but suffers many of the same drawbacks as using a single DNS namespace. And you're involving more DNS servers into the resolution process for what purpose again? -ASB: http://XeeSM.com/AndrewBaker Sent from my Motorola Droid On Apr 28, 2010 12:51 PM, "Joseph Heaton" <[email protected]> wrote: Andrew, So you don't recommend the subdomain? Also, if you could expand on your answer, it'd be great, as I'm bringing all ideas to a meeting this afternoon, with pros/cons behind each option. >>> "Andrew S. Baker" <[email protected]> 4/28/2010 8:55 AM >>> Use two separate domain names, even if you register the internal one. You can avoid all manner of p... the Novell guy is saying. Is that still true today? We are on private IPs internally, so external forces can't route to the inside an... ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com... ~ 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/> ~
