New Domain Name

[Joshua Astete]

I have a Windows 2000 domain named: domainname.local. I about to setup an
Exchange server and upgrade my domain to Windows 2003. My company website
is hosted by a third party company, with name domainname.com.

I have 2 questions:

1. Can I have my website point to a different location then my email
server? If so then how do I accomplish this?

2. How do I configure my exchange server to add my Internet domain to the
end of all my users? How do I configure Exchange to send email as
domainname.com instead of domainname.local?

Help Please.

 

[Lanwench [MVP - Exchange]]

I have a Windows 2000 domain named: domainname.local. I about to
setup an Exchange server and upgrade my domain to Windows 2003. My
company website is hosted by a third party company, with name
domainname.com.

I have 2 questions:

1. Can I have my website point to a different location then my email
server? If so then how do I accomplish this?

Yes - most small companies don't host their own public websites. Since
you're using domain.local, not domain.com, in your AD DNS, anyone on your
LAN should be able to find www.domain.com without your needing to do
anything, presuming your internal DNS is set up properly. That means, all
servers and workstations should specify *only* the internal AD-integrated
DNS server's IP address in their network settings. The AD-integrated DNS
server should be set up with forwarders to your ISP's DNS servers for
external resolution.

2. How do I configure my exchange server to add my Internet domain
to the end of all my users? How do I configure Exchange to send
email as domainname.com instead of domainname.local?

Add domain.com to your recipient policy and set it as the default. Presuming
you haven't removed the "inherit changes from recipient policy" (paraphrase)
from each user's ADUC properties on the Exchange box, they should all get
it. By default, the e-mail address format will be <exchange
alias>@domain.com - if you need to change that, you can -

 

[Joshua Astete]

Thanks for all the help. Wow! I apologize for posting in multiple forums.
Won't happen again. Thanks again.



"Lanwench [MVP - Exchange]"

 

[Lanwench [MVP - Exchange]]

Thanks for all the help.

Most welcome!

Wow! I apologize for posting in multiple

forums. Won't happen again. Thanks again.

I don't think I saw your multiposts, but they do tend to make people cranky.
If you need to post to multiple groups, it's best to crosspost instead, by
posting a single message to a handful of relevant groups (separate the NG
names with commas) so that everyone can follow the thread.

"Lanwench [MVP - Exchange]"

Yes - most small companies don't host their own public websites.
Since you're using domain.local, not domain.com, in your AD DNS,
anyone on your LAN should be able to find www.domain.com without
your needing to do anything, presuming your internal DNS is set up
properly. That means, all servers and workstations should specify
*only* the internal AD-integrated DNS server's IP address in their
network settings. The AD-integrated DNS server should be set up with
forwarders to your ISP's DNS servers for external resolution.

Add domain.com to your recipient policy and set it as the default.
Presuming you haven't removed the "inherit changes from recipient
policy" (paraphrase) from each user's ADUC properties on the
Exchange box, they should all get it. By default, the e-mail address