myDomain.com website and poop3 is hosted by ISP but I am talking over soon...

And i'm installing a w2K domain now. Shall I use the registered dmoain.name for the new intenral w2k domain even though the name is currently in use with pop3...? I will be installing Exchange 2000 and will redirect all the pop3 to new Exchange server.

"Stephan Barr" wrote:
And i'm installing a w2K domain now. Shall I use the registered
dmoain.name for the new intenral w2k domain even though the name is
currently in use with pop3...? I will be installing Exchange 2000 and will
redirect all the pop3 to new Exchange server.

Please only use plain text in NGs.

No. Internal and external names should be separtate. A split horizon is
not the best solution.
The internal domain needs to be dotted.
Ex. domain.internal, domain.local, internal.domain.com <-(my preference)

In the Exchange, I create addresses for external and internal domains but
set default to external so when someone replies, it goes to the external
domain. If you set the default to the internal address, then it bounces
since the Internet does not have information for user@internal.domain.com.
There is no reason for email from internal, to internal, to go external so
address internal mail to user@internal.domain.com.

All workstations/servers should only have DNS set to internal DNS. DNS
should be on the main AD server. Only reference ISP's DNS servers
[optional] with a forwarder in the DNS server settings. Make sure the root
entry "." in the forward lookup zone is not present. If you eliminate
creating a forwarder, the root hint servers will be used for Internet
naming.

HTH...

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servic...sp?fr=0&sd=tech