• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 390
  • Last Modified:

I need to know how to set up DYNDNS with MS Exchange Server 2003 ( To get the full mission accomplish)

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!!!
  • 2
1 Solution

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)

Quite easy to do - I have been hosting Exchange at home on a dynamic IP address for the last four years.

First - setup one of the tool for keeping dyndns.org up to date with your IP address. I usually set this is on the Exchange server.
Second- Configure your MX records to use the dyndns.org host name that you created. MX records don't have to be in the same domain as your domain.
Third - As you are on a dynamic IP address, you will have to use an SMTP Connector to send email via your ISP. Don't even bother trying to send email directly as many places will not accept your email messages.

If you want to do other inbound things, like OWA etc, then setup an ALIAS (CNAME) on your domain for a host, and alias it to your dyndns.org address.
For example, mail.domain.com could be aliased to host.dyndns.org

Raghu - a lot of us cannot have static IP addresses. The ISP that I was with didn't even offer the facility unless you took out a business account which would cost two or three times the home user account. For my home Exchange server it wasn't worth the outlay. As long as you appreciate that many sites will block the traffic and use an SMTP Connector instead, you can operate quite happily on a dynamic IP.


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.


Featured Post

Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now