The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

MX records for sub-domains

Discussion in 'General Discussion' started by rezman, May 25, 2012.

  1. rezman

    rezman Well-Known Member

    Joined:
    Feb 3, 2011
    Messages:
    45
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    USA
    cPanel Access Level:
    Root Administrator
    Trying to follow up from an old thread that I couldn't reply to.

    Edit DNS Zone Subdomain MX Records

    I'm having a very strange problem with an client and it seems to have something to do with this.

    They have their root domain of "domain.com"
    They created a sub-domian of "register.domain.com"
    They pointed the CNAME for "register.domain.com" over to an amazonaws.com address.

    They also want to use Gmail for the sub-domains email so they added in the following MX entries into Cpanel

    Code:
    register        7200    IN      MX      1       ASPMX.L.GOOGLE.COM.
    register        7200    IN      MX      5       ALT1.ASPMX.L.GOOGLE.COM.
    register        7200    IN      MX      5       ALT2.ASPMX.L.GOOGLE.COM.
    register        7200    IN      MX      10      ASPMX2.GOOGLEMAIL.COM.
    register        7200    IN      MX      10      ASPMX3.GOOGLEMAIL.COM.
    Up to this point everything looks fine however DNS doesn't seem to be loading the MX records when I do a dig lookup. In fact I get the following

    Code:
    # dig MX register.domain.com
    
    ;; QUESTION SECTION:
    ;register.domain.com.          IN      MX
    
    ;; ANSWER SECTION:
    register.domain.com.   961     IN      CNAME   appidxxxxxxherokucom-xxxxxxx.us-east-1.elb.amazonaws.com.
    
    ;; AUTHORITY SECTION:
    appidxxxxxherokucom-xxxxxx.us-east-1.elb.amazonaws.com. 43 IN SOA ns-947.amazon.com. root.amazon.com. 1337968855 3600 900 7776000 60

    Code:
    # dig register.domain.com
    
    ;; QUESTION SECTION:
    ;register.domain.com.          IN      A
    
    ;; ANSWER SECTION:
    register.domain.com.   1800    IN      CNAME   appidXXXXXXherokucom-464674771.us-east-1.elb.amazonaws.com.
    appidXXXXXXherokucom-XXXXXX.us-east-1.elb.amazonaws.com. 60 IN A 23.23.235.194
    appidXXXXXXherokucom-XXXXXX.us-east-1.elb.amazonaws.com. 60 IN A 107.22.179.197
    appidXXXXXXherokucom-XXXXXX.us-east-1.elb.amazonaws.com. 60 IN A 23.21.74.78
    
    ;; AUTHORITY SECTION:
    elb.amazonaws.com.      2089    IN      NS      ns-925.amazonaws.com.
    elb.amazonaws.com.      2089    IN      NS      ns-944.amazonaws.com.
    elb.amazonaws.com.      2089    IN      NS      ns-941.amazonaws.com.
    elb.amazonaws.com.      2089    IN      NS      ns-935.amazonaws.com.
    elb.amazonaws.com.      2089    IN      NS      ns-934.amazonaws.com.
    elb.amazonaws.com.      2089    IN      NS      ns-947.amazonaws.com.
    elb.amazonaws.com.      2089    IN      NS      ns-916.amazonaws.com.
    elb.amazonaws.com.      2089    IN      NS      ns-927.amazonaws.com.
    
    ;; ADDITIONAL SECTION:
    ns-947.amazonaws.com.   9962    IN      A       204.246.162.10
    
    Why or how is it over riding the DNS AUTHORITY SECTION and putting Amazon's NS servers in there? That should be the DNS server of 'domain.com'.

    Below is the root domain's 'domain.com' info.
    Code:
    # dig domain.com
    
    ;; QUESTION SECTION:
    ;domain.com.                   IN      A
    
    ;; ANSWER SECTION:
    domain.com.            74      IN      A       209.xxx.xx.xx
    
    ;; AUTHORITY SECTION:
    domain.com.            19874   IN      NS      cpanel2.host.net.
    domain.com.            19874   IN      NS      cpanel1.host.net.
    
    ;; ADDITIONAL SECTION:
    cpanel1.host.net.     50653   IN      A       209.xxx.xx.xx
    cpanel2.host.net.     53053   IN      A       209.xxx.xx.xx
    
     
    #1 rezman, May 25, 2012
    Last edited: May 25, 2012
Loading...

Share This Page