how to prevent changes at /etc/localdomains during DNS editing at WHM. Cpanel 11

Same here, we have a spamAppliance and it is doing the same when we make any DNS change, it simply removes it from localdomains and adds to remotedomains.

Is there some feature to disable this?

This is a great feature for people switching to a exchange box or gmail or such, but this looks like it will be very very problematic for our application.

 

bump.. We are also having the same problem with Cpanel11. The customer users separate servers for just doing spam filtering, but the cpanel server is the final delivery mail server.

Any ideas?

 

Thanks for your response. I'm running the latest RELEASE, its not in there. I will look forward to the next RELEASE and hopefully it will be there.

 

Ok that makes sense. But if the domain is not owned by a user, why would it try to disable local mail delivery for that domain? It seems like it should check to see if the domain is hosted locally before trying to disable email delivery.

 

Do you guys plan on making a option so that it will never goto the remotedomains file in case we are using a spam filtering appliance or such that will then relay mail to the server?

 

Thanks Nick!!

 

This doesn't seem to be true, regardless of whether "Automatically setup /etc/localdomains, /etc/remotedomains, /etc/secondarymx based on where the mx entry is pointed." is checked in Tweak Settings or not.

If we edit the DNS on domain for which no changes have been made since CP 11, the "Always accept mail locally even if the primary mx does not point to this server. " box is always unchecked. So ANY change made to the DNS settings halts local mail delivery unless the person doing the editing happens to notice the incorrect status of the checkbox. This also happens by simply opening the Edit DNS page and then clicking save without making any changes.

If we edit the DNS on domain that has been edited after CP 11 installation it will correctly report the status in the "Always accept mail locally even if the primary mx does not point to this server." checkbox.

Those behaviors do not change after changing the Tweak Settings checkbox.

We are using 11.4.18-C14158.

Scott

 

Same Here

My guess is that maybe if you use the default whm dns behaviour of making the primary mail server the same as the domain name
eg domain. mx 0 domain.
instead of what many people use
eg domain. mx 0 mail
then possibly the problem will go away (untested yet)

Not sure that the info in an earlier post is true; ie "that as long as your lowest numbered mx is pointing to an ip on that server" (or something like that); as this is the case on mine, but definitely moved the domain from locadomains to remotedomains when I did one edit of the customer's dns.

 

this statement does not prove as correct on my cpanel server

so dns says

domain. MX 0 mail
mail A serverip

serverip is an aliasip on the server

took the domain out of localdomains and put it in remotedomains when dns was updated with an unrelated new entry

 

Well, In my case, putting:
domain. mx 0 mail.

solves the problem. After save the data I get "This server will serve as the primary mail exchanger" and is listed in localdomains.

Thank you very much for the tip.