DH figures prominently in my plans to ditch my expensive static-IP ADSL in favor of less-expensive, higher-bandwidth dynamic ADSL service.
However, I have questions about how to maintain my public-facing environment after the cut. So I am hoping for a little help from the experts...please?
My edge is an ISA 2004 firewall which I would like to continue to use after the cut, even if it's behind something like a LinkSys DDNS client.
Behind the firewall, the first of two IIS 6 servers hosts four HTML sites on different domains. Those sites can move to DH.
The other webserver provides SSL pass-through authentication to business data on my Windows file server. Those files have to stay in my office.
I also have an Exchange 2003 server. External users retrieve their mail via browsers, IMAP-S, and Outlook RPC over HTTPS sessions.
My business domain receives around a thousand messages each day, mostly spam, but the rest of the traffic is critical. To guard against outage, this domain has a secondary MX pointed at a store-and-forward server hosted elsewhere. Daily outbound traffic is typically less than 50 messages, and it's important that the outbound mail scores low on my recepient's spam filters. I've had a reverse pointer and an SPF record for years.
The rest of the domains don't receive much spam, and very little legitimate traffic. However, one of the domains sends out a band mailing list to 1,000 subscribers almost every week and that needs to appear legitmate to avoid blockage.
The questions I have are, how closely can I mimic my current environment once I cut over to dynamic IP service, and what services does DH offer that are of use in this quest?
Thank you very much!