Hi,
Got a strange server scenario but I sure someone will able to point me in the right direciton.
I have been playing around with a Win2k3 Domain Controller that will also host an Exchange 2003 server (my own test system so keeping things on one box).
I originally had the DC configured with same domain name as my registered internet domain name e.g:
LAN Domain: mydomain.com
Registered Domain Name: mydomain.com
I then installed and configured an Exchange 2003 server on this DC so I could host my personal emails using the mydomain.com tld e.g: someone@mydomain.com - this all worked fine and I was able to send and receive email correctly.
However I had a recent disk failure and the drive containing Win2k3 failed so I had to rebuild the server. I renamed the Exchange Server directory so I would later be able to do an online restore (which worked fine).
During the setup of the DC I decided to go with the default textbook name of mydomain.local thinking this would be a good way of segregating the local domain from the public domain (the .com domain name).
I set everything up including DNS and registered the LAN PC's to the new DC which all went well. I think proceeded to setup the Exchange 2003 server - this would host emails for the finalzero.com domain; I configured the Internet Messaging and SMTP protocol to point to mydomain.com. However when I tried to send or receive mail nothing seemed to go through.
I had created a forward lookup zone for the public domain name in the DNS snap-in i.e. mydomain.com so I had two zone:
mydomain.local
mydomain.com
When I tried to send an email from an external web mailbox I received postmaster emails advising the emails were undeliverable to the address <somename>@mydomain.com (the .com domain has always been hosted on a 3rd party dedicated server).
I decided to ditch the above and rebuild the server as it was previously wtih the LAN domain being the same as the public domain however I am curious if the above method works and what I need to do to get that kind of setup working i.e:
1. Have a local area DC hosting mydomain.local
2. Have the Mail Server host local email and route to the public .com domain name (and vice versa accepting incoming emails to the .com domain and routing them to the .local addresses).
Thanks in advance,
Fz
Got a strange server scenario but I sure someone will able to point me in the right direciton.
I have been playing around with a Win2k3 Domain Controller that will also host an Exchange 2003 server (my own test system so keeping things on one box).
I originally had the DC configured with same domain name as my registered internet domain name e.g:
LAN Domain: mydomain.com
Registered Domain Name: mydomain.com
I then installed and configured an Exchange 2003 server on this DC so I could host my personal emails using the mydomain.com tld e.g: someone@mydomain.com - this all worked fine and I was able to send and receive email correctly.
However I had a recent disk failure and the drive containing Win2k3 failed so I had to rebuild the server. I renamed the Exchange Server directory so I would later be able to do an online restore (which worked fine).
During the setup of the DC I decided to go with the default textbook name of mydomain.local thinking this would be a good way of segregating the local domain from the public domain (the .com domain name).
I set everything up including DNS and registered the LAN PC's to the new DC which all went well. I think proceeded to setup the Exchange 2003 server - this would host emails for the finalzero.com domain; I configured the Internet Messaging and SMTP protocol to point to mydomain.com. However when I tried to send or receive mail nothing seemed to go through.
I had created a forward lookup zone for the public domain name in the DNS snap-in i.e. mydomain.com so I had two zone:
mydomain.local
mydomain.com
When I tried to send an email from an external web mailbox I received postmaster emails advising the emails were undeliverable to the address <somename>@mydomain.com (the .com domain has always been hosted on a 3rd party dedicated server).
I decided to ditch the above and rebuild the server as it was previously wtih the LAN domain being the same as the public domain however I am curious if the above method works and what I need to do to get that kind of setup working i.e:
1. Have a local area DC hosting mydomain.local
2. Have the Mail Server host local email and route to the public .com domain name (and vice versa accepting incoming emails to the .com domain and routing them to the .local addresses).
Thanks in advance,
Fz