G
Giganews
I am running W2K SP4 in a native AD on two subnets connected via WAN link.
I am running SQL 2000, two SPPS 2001 servers, Exchange 2003 etc.
Way back when, and even recently, it was advisable to name an internal
domain domain.local (if you don't believe me look at SBS 2003 document.)
Given some of the advanced functionality of ISA (Exchange RPC publishing for
example) it would be nice to be running a split domain.
So, currently I am running domain.local internally and domain.com, using my
ISP DNS servers, externally. I am trying to determine how I can either
change the suffix from domain.local to domain.com or emulate a split domain.
So far here is what I have found may be possible:
1. Upgrade to Server 2003 AD and use rendom.exe (although it is stated that
it is not supported with Exchange installed.).
2. Install a side by side domain and migrate over (Although I would like to
keep the same NetBIOS name so this does not sound possible either).
3. Add domain suffix search orders to every computer. ( I have done this
and it helps when the laptops are offsite as they then are using a valid
".com" to lookup host names. However, the internal server returns the FQDN
of mail.local which throws everything for a loop).
4. Change the "primary domain suffix" for every computer on the network and
leave the AD structure as "domain.local". (I am not sure if this will work,
especially if I change the primary domain suffix of the servers, except the
DCs of course which can not be changed. Also, how will this affect my DDNS,
would I have to create a second forward lookup zone to allow the computers
to register their names?)
Anyone have ANY thought on these, especially #4.
I am seriously considering paying $250 and speaking with PSS on this issue!
Thanks,
Bob
PS For anyone reading this I would NEVER use domain.local in an AD setup
again. it is MUCH easier to mirror your external domain. Especially when
you have laptops that roam outside of your network......
I am running SQL 2000, two SPPS 2001 servers, Exchange 2003 etc.
Way back when, and even recently, it was advisable to name an internal
domain domain.local (if you don't believe me look at SBS 2003 document.)
Given some of the advanced functionality of ISA (Exchange RPC publishing for
example) it would be nice to be running a split domain.
So, currently I am running domain.local internally and domain.com, using my
ISP DNS servers, externally. I am trying to determine how I can either
change the suffix from domain.local to domain.com or emulate a split domain.
So far here is what I have found may be possible:
1. Upgrade to Server 2003 AD and use rendom.exe (although it is stated that
it is not supported with Exchange installed.).
2. Install a side by side domain and migrate over (Although I would like to
keep the same NetBIOS name so this does not sound possible either).
3. Add domain suffix search orders to every computer. ( I have done this
and it helps when the laptops are offsite as they then are using a valid
".com" to lookup host names. However, the internal server returns the FQDN
of mail.local which throws everything for a loop).
4. Change the "primary domain suffix" for every computer on the network and
leave the AD structure as "domain.local". (I am not sure if this will work,
especially if I change the primary domain suffix of the servers, except the
DCs of course which can not be changed. Also, how will this affect my DDNS,
would I have to create a second forward lookup zone to allow the computers
to register their names?)
Anyone have ANY thought on these, especially #4.
I am seriously considering paying $250 and speaking with PSS on this issue!
Thanks,
Bob
PS For anyone reading this I would NEVER use domain.local in an AD setup
again. it is MUCH easier to mirror your external domain. Especially when
you have laptops that roam outside of your network......