BIND DNS records for new domains getting ignored.

Hi,

Custom BIND DNS records for new domains getting ignored for alias servers if main server have different mx records. I had google app mx records for main domains but after they removed free version, i changed my Server Template to use yandex mx records but when i create an alias for old domains those are using google apps, alias domain creation is just ignoring new mx records and using main domain's google mx records.

My old setting for BIND DNS records for new domains:

;
; Gmail mx records
;
${DOM}. IN MX 1 ASPMX.L.GOOGLE.COM.
${DOM}. IN MX 5 ALT2.ASPMX.L.GOOGLE.COM.
${DOM}. IN MX 5 ALT1.ASPMX.L.GOOGLE.COM.
${DOM}. IN MX 10 ASPMX2.GOOGLEMAIL.COM.
${DOM}. IN MX 10 ASPMX3.GOOGLEMAIL.COM.

posta IN CNAME ghs.google.com.

My new setting for BIND DNS records for new domains:

;
; Yandex mx records
;
${DOM}. IN MX 10 MX.YANDEX.NET.

mail IN CNAME domain.mail.yandex.net.
Status: 
Active

Comments

For alias domains, the DNS records are always copied from (and kept in sync with) the target domain. I don't see how it would make sense for the alias to use different MX servers from the real target domain?

I am using Wordpress Multisite and actually these sites can have different mail providers. Some using google, some of them are yandex..

So its a problem for me :S

I see ... unfortunately, having an alias domain that shares a website but has separate DNS records isn't currently supported in Virtualmin. That said, you should be able to edit the records after creation at Webmin -> System -> BIND DNS Server.