I just fiddled with a test account and can confirm, at least for me, that when choosing to edit an MX record, the contents of /etc/localdomains and /etc/remotedomains are updated correctly based on whether the MX record resolves locally. However when editing a whole DNS zone, and then changing the MX record, nothing else other than the zone file appears to get changed.

In response to the very first post: best go for editing an MX record only!

I just fiddled with a test account and can confirm, at least for me, that when choosing to edit an MX record, the contents of /etc/localdomains and /etc/remotedomains are updated correctly based on whether the MX record resolves locally. However when editing a whole DNS zone, and then changing the MX record, nothing else other than the zone file appears to get changed.

In response to the very first post: best go for editing an MX record only!

Click to expand...

Does this also occur when using the cpanel utility to change mx record? (ie: If the end customer makes the change themselves?)

Thanks!

I am an eNom ETP.Sign up today if you want an eNom.com domain reseller account from a reliable provider.* We now provide support and service to over 3250 happy resellers!