MX Subzone DNS Setup on xname.org

Question

I've a zone example.tld configured with a wildcard CNAME (1&1), A records (custom & 1&1), MX records (1&1), and a subzone record (NS) pointing to ns1.xname.org.

I've configured the subzone subzone.example.tld conatining a MX record pointing to a NAS. I've added a sub-zone record (not sure if necessary)

However, when I dig to it using dig @ns1.xname.org subzone.example.tld in mx, I obtain MX records of example.tld.

How can I fix my configuration to have subzone MX records taken in account ?

I've tried dig @ns1.xname.org subzone.example.tld in ns with negative results :

;; ANSWER SECTION:
subzone.example.tld.    86400   IN  CNAME   example.tld.
example.tld.    86400   IN  NS  ns2.xname.org.
example.tld.    86400   IN  NS  ns0.xname.org.
example.tld.    86400   IN  NS  ns1.xname.org.

Zone configuration (example.tld):

$TTL 86400 ; TTL par défaut
example.tld.        IN  SOA ns0.xname.org.  . (
                1234567891  ; numéro de série
                10800   ; Intervalle de rafraichissement
                3600    ; Intervalle de renouvellement de tentative
                604800  ; Délai d'expiration
                10800   ; TTL pour les réponses négatives
            )

$ORIGIN example.tld.
            IN      NS      ns1.xname.org.
            IN      NS      ns0.xname.org.
            IN      NS      ns2.xname.org.
        10  IN      MX  0   mx00.1and1.fr.
        10  IN      MX  1   mx01.1and1.fr.
example.tld.            IN      A       12.34.56.67




*           IN      CNAME       example.tld.


subzone         IN      NS      ns1.xname.org.

Subzone (subzone.example.tld)

$TTL 86400 ; TTL par défaut
subzone.example.tld.        IN  SOA ns0.xname.org.  . (
                1234567890  ; numéro de série
                10800   ; Intervalle de rafraichissement
                3600    ; Intervalle de renouvellement de tentative
                604800  ; Délai d'expiration
                10800   ; TTL pour les réponses négatives
            )

$ORIGIN subzone.example.tld.
            IN      NS      ns2.xname.org.
            IN      NS      ns0.xname.org.
            IN      NS      ns1.xname.org.
            IN      MX  0   mx.subzone.example.tld.
mx          IN      A       1.2.3.4

Answer 1

I added your zones (in their current state, after Joel Coel's edit) into my bind 9.7.3. It does return MX record:

;; QUESTION SECTION:
;subzone.example.tld.       IN  MX

;; ANSWER SECTION:
subzone.example.tld.    86400   IN  MX  0 mx.subzone.foo.tld.

;; AUTHORITY SECTION:
subzone.example.tld.    86400   IN  NS  ns0.xname.org.
subzone.example.tld.    86400   IN  NS  ns1.xname.org.
subzone.example.tld.    86400   IN  NS  ns2.xname.org.

It seems that there's just some mistake, maybe your new zone file doesn't appear on the server yet, or there's some typo not shown here or it's a bug in their bind version or something like that.

I'm not sure though why you need such delegated subzone (like BillThor suggested).

Answer 2

There are two ways to define your subdmain. They way you are specifying requires you to specify the NS servers for the subdomain in the parent domain.

The alternate method is to just define it within the parent domain.

subdomain     IN MX   10  mx.subdomain.example.tld
mx.subdomain  IN A    192.0.2.4

or self MX

subdomain     IN MX   10  subdomain.example.tld
              IN A    192.0.2.4      

or MX defined in parent domain

subdomain     IN MX   10  mx.example.tld
mx            IN A    192.0.2.4

The second method is commonly used when the subdomain refers to a host or service. The first method us normally reserved when delegating a subdomain to a different DNS administrator and/or different name servers.

Answer 3

I dont see an MX record in the code that you provided, also MX records dont like CNAMES ... so what you need to is :

subzone.example.tld. 86400 IN MX 10 foo.tld.