Edit Zone Templates - MX Problem
This is where you set up your MX in zone templates:
%domain%. %ttl% IN MX 0 %domain%.
I changed it to:
%domain%. %ttl% IN MX 0 %maildomain%.
When I add a new domain to cPanel, the MX value is still example.com, not mail.example.com. Is there any way to make this setting work?
-
Hey hey! Did you make sure to use the "standardvirtualftp" template when you made these changes? Also, %maildomain% is "the hostname of the server that handles the domain’s mail" so it could be that it's pulling the correct value and that value just isn't what you expect.
When I edit the template on my end to add a random record to a new domain, I'm seeing the same behavior as you in the zone:
totallyrandomdomain.com. 14400 IN TXT "totallyrandomdomain.com"
so I'm guessing it's more of an issue with the variable not pulling the expected content. Can you let me know what you're hoping for that variable to pull?
0 -
If Vatra is wanting the MX's to be created pointing to mail.domain.com instead of domain.com
1. Make sure you add an appropriate mail.domain.com A-record pointing to the IP address of the server
2. That template modification doesn't look correct. Maybe they really want:
%domain%. %ttl% IN MX 0 mail.%domain%.
If the domain is xyz.com, that should create an MX record, priority 0, referencing mail.xy.com
1 -
I've made the same change in all three templates.
I thought that %maildomain% was mail.example.com. That is what I want to pull. mail.%domain% was a solution.
Note: My server's hostname, server.example.com, handles outgoing mail by default. But MX is about incoming mail, and regardless of what I put in the template: %domain% or %maildomain%, the domain's apex is pulled, not the server hostname.
1 -
I think that is what is supposed to happen here - I also use mail.%domain% when I want to manually make it into the mail subdomain to use a custom MX record elsewhere.
1
Please sign in to leave a comment.
Comments
4 comments