What you need to do this is nat reflection (IIRC) which ebox doesn't do at the moment.
What is happening is that your lan clients are using backup.halconrealestate.com which points at your public ip rather than the internal ip of your mailserver.
There are two hacks that let you get round this:
- Just use the internal ip rather than the hostname for your internal lan machines. This is fine for desktop machines that are always inside your lan but won't work with laptops that need to access the server inside and outside your lan.
- Do some tricks with DNS... I assume you've got the nameservers for halconrealestate.com on some host on the internet (rather than the ebox where you're setting up your backup server). Make a note of all the hostnames you've got on there. Then go to the DNS server section of your backup ebox and recreate them all for your domain there BUT change the backup.halconrealestate.com entry to point at the internal IP of your mailserver.
As long as your lan clients are using ebox for their DNS they will now think that
www.halconrealestate.com is at the normal IP of your webserver while using the private IP for your backup server. If a laptop is used outside your lan then it will use the public DNS server which has the public ip of your mailserver.
Two small problems with this:
Laptops have to get their DNS through DHCP, you can't set them to use OpenDNS etc.
Changing the IP of one your servers will require updating 2 lots of DNS settings.