Problems with default MX Zone

fabweb

Verified User
Joined
Jul 16, 2019
Messages
6
Hello,
we are migrating part of our cPanel framework to directadmin. We chose to use cPanel DNS Cluster.
Whenever I restore a DirectAdmin backup from cpanel the MX entries do not work.
I tried to edit dns_mx.conf to "host-name.com=10" but it still doesn't work.

Has anyone ever experienced this?

PS: Sorry if I posted in the wrong place.
 
Hello,

The server creates the MX entry like this:
domain.tld. MX 10 mail

I think the correct would be the example:
domain.tld. MX 10 mail.domain.tld. or
domain.tld. MX 10 hostname.com.
 
The record is correct in bind9/named syntax

Code:
domain.tld. MX 10 mail

it's the same as

Code:
domain.tld. MX 10 mail.
Code:
[COLOR=#333333]domain.tld.[/COLOR]


If you use a custom script to sync zones to remote DNS services then you might need to change it to a FQDN.

In this case copy
/usr/local/directadmin/data/templates/dns_mx.conf to /usr/local/directadmin/data/templates/custom/ and update the /usr/local/directadmin/data/templates/custom/dns_mx.conf

Code:
mail.|DOMAIN|.=10

It will effect only new domains created on a server. You will need to take additional actions to update existing ones whenever it's required.
 
The record is correct in bind9/named syntax

Code:
domain.tld. MX 10 mail

it's the same as

Code:
domain.tld. MX 10 mail.
Code:
[COLOR=#333333]domain.tld.[/COLOR]


If you use a custom script to sync zones to remote DNS services then you might need to change it to a FQDN.

In this case copy
/usr/local/directadmin/data/templates/dns_mx.conf to /usr/local/directadmin/data/templates/custom/ and update the /usr/local/directadmin/data/templates/custom/dns_mx.conf

Code:
mail.|DOMAIN|.=10

It will effect only new domains created on a server. You will need to take additional actions to update existing ones whenever it's required.

Thank you. I will try this now.
 
Back
Top