Incorrect behavior for CNAME records ISPConfig 3

Discussion in 'General' started by kpowney, Apr 7, 2012.

  1. kpowney

    kpowney New Member

    I have a server running Debian 6 and ISPConfig 3.04.3. The server was built using the Perfect Server Debian 6 Bind and Dovecot instructions. All functions of the server work as expected except for fail2ban and resolution of CNAME dns records. I haven't looked into fail2ban yet and to be honest it is the least of my concerns at the moment.

    My concern is with the CNAME record resolution. Currently dns responses are appending my current domain name to the end of the cname data record. For example sub.domain.tld resolves as cnamedata.tld.domain.tld. from what I can tell the zone file in bind is correct. This occurs for all cname records in either of the two zones I have currently on the server.

    For example:

    Zone domain1.tld file contains a record as follows:
    mail 86400 CNAME mail.domain1.tld.

    Zone domain2.tld contains:
    home 86400 CNAME home.dynamicdns.tld

    DNS resolution:
    $nslookup mail.domain1.tld

    Non-authoritative answer:
    mail.domain1.tld canonical name = mail.domain1.tld.domain1.tld.
    Name: mail.domain1.tld.domain1.tld
    Address: 72.20.x.x

    $nslookup home.domain2.tld

    Non-authoritative answer:
    home.domain2.tld canonical name = home.dynamicdns.tld.domain2.tld.
    Name: home.dynamicdns.tld.domain2.tld.
    Address: 72.20.x.x (should be 67.177.x.x)

    If needed I can provide domain information and exact zone files, but I would prefer to keep them private if possible as one of the records should resolve to my home IP. Any help or advise on figuring this out would be appreciated.


  2. falko

    falko Super Moderator ISPConfig Developer

    You've forgotten a dot. The record must be:

    home     86400     CNAME     home.dynamicdns.tld[COLOR="Red"].[/COLOR]
    BTW, MX records must not point to CNAME records - only A records are allowed.
  3. kpowney

    kpowney New Member



    thanks for the reply that is exactly what I did. I left off the trailing '.' on all of the CNAME records. I actually found the issue last night but didn't get a chance to post the solution.

    In regard to CNAME and MX records is there a reason CNAME records shouldn't be pointed to MX records? The MX record itself resolves to an A record. I also haven't had any issues sending or receiving mail from either domain.

  4. falko

    falko Super Moderator ISPConfig Developer

Share This Page