dykirin
asked on
I need to know how to set up DYNDNS with MS Exchange Server 2003 ( To get the full mission accomplish)
Hello,
I have recently created account with http://www.dyndns.com/ I would like to host MS Exchange server 2003 inside my network locally. At first I thought you can only host Email or web servers inside your network only if you have a static IPs. Someone advise I can host an email server inside my network locally with WAN DHCP. Can someone please help me accomplish this theory? I have already created DYNDNS at this URL http://www.dyndns.com/ I need to know all basic setup MS-RECORD, A-RECORD with the domain registrar, How to config with my router, any port forwarding ....etc. Please help ASAP!!!
I have recently created account with http://www.dyndns.com/ I would like to host MS Exchange server 2003 inside my network locally. At first I thought you can only host Email or web servers inside your network only if you have a static IPs. Someone advise I can host an email server inside my network locally with WAN DHCP. Can someone please help me accomplish this theory? I have already created DYNDNS at this URL http://www.dyndns.com/ I need to know all basic setup MS-RECORD, A-RECORD with the domain registrar, How to config with my router, any port forwarding ....etc. Please help ASAP!!!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Simon,
Agreed to all the point that you have put across, although expecting less of trouble i had to put across the static IP option.
If the ISP allows to smart host then i guess i have mentioned that anyways. adding a CNAME record would be an advantage for OWA and OMA.
Raghu
Agreed to all the point that you have put across, although expecting less of trouble i had to put across the static IP option.
If the ISP allows to smart host then i guess i have mentioned that anyways. adding a CNAME record would be an advantage for OWA and OMA.
Raghu
If DYNDNS provides you one fixed IP as your public identity then it would be possible to host the exchange server. I would still advise you to purchase a static IP from youe ISP since most of the major domains in the internet reject emails originating from any pool of Dynamic IP.
I had once tried using no-ip services and ended up blacklisting that IP and ould not send emails to a lot of external domains.
In case you still wish to expriment, you would have to create an "A" record associating your external IP to domain, MX record associating to public IP that will route email to your exchange (wan to lan NAT required for email to hit exchange), and a reverse PRT record corrsoponding to your outgoing IP (if this is not created you would not be able to send email to aol, yahoo, comcast, earthlink etc)
Raghu