I've noticed this morning that our dns records do not specify a secondary mail exchanger record (mx).
Output of nslookup:
CODE
U:\>nslookup
Default Server: falcon.mhxs.mhx
Address: 203.14.37.4
> set type=mx
> volutin.net
Server: falcon.mhxs.mhx
Address: 203.14.37.4
Non-authoritative answer:
volutin.net MX preference = 0, mail exchanger = volutin.net
volutin.net nameserver = ns10.hostony.net
volutin.net nameserver = ns11.hostony.com
volutin.net internet address = 209.152.180.21
>
Default Server: falcon.mhxs.mhx
Address: 203.14.37.4
> set type=mx
> volutin.net
Server: falcon.mhxs.mhx
Address: 203.14.37.4
Non-authoritative answer:
volutin.net MX preference = 0, mail exchanger = volutin.net
volutin.net nameserver = ns10.hostony.net
volutin.net nameserver = ns11.hostony.com
volutin.net internet address = 209.152.180.21
>
This means that when our servers are down (especially for extended periods of time), there is a possibility that mail will bounce back to the sender. I know that most servers will try to resend the message for anywhere up to 4 days, but this is not acceptable.
It should be relatively easy for hostony to set up one server that can be set as backup mx for all of hostony's servers - it shouldn't be under too high a load, as long as uptime of the rest of the servers is ok.
Could you please advise as to whether this is possible. If it isn't, could you please outline the reasons why.
Regards,
Will