Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Currently we keep a DNS rule for every client that has and this helps us redirect their mail to another server like GMail if they don't want to use our server. The problem is that when these domains change IPs or their individual SSL certs expire they can be locked out of their e-mail or have to confirm security exceptions they don't remove later.

To summarize we have something like this as DNS records:    MX <-- sometimes changes for people with GMail

The plan is we move our clients to using a single hostname for connecting to the mail server. So instead all clients would always connect to - This seems to work fine for new clients, as we tell them the new address to use, but for older clients we want to avoid clients having to change their settings.

If we change the MX record to go to the same host as will our clients reject this?

share|improve this question
What the what? Sorry, but I'm not following your question; I think you've got some DNS concepts mixed up. Clients don't use MX records at all, only mail servers do, specifically MTA (SMTP) servers. You can only ensure SSL or TLS connections between devices you control and others. You can't guarantee encryption outside that area of control. Perhaps if you take a step back and describe the policy or problem you're trying to implement/solve instead of the half-solution you've got going it would help to clarify your situation. – Chris S Aug 14 '12 at 18:34
Sorry, when I said clients above I meant client DNS configuration on the server we host for them – Kristopher Ives Aug 14 '12 at 22:44

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.