ISPconfig & Zone Files - Bugs?

Discussion in 'General' started by DOCK, Mar 29, 2007.

  1. DOCK

    DOCK New Member

    Hi,

    today I found a few things on our ISPconfig driven server which made me worrying…

    First… when I try to "dig @127.0.0.1 MX domain.tld" on our server, I get:

    Code:
    
    # dig @127.0.0.1 MX domain.tld
    
    ;; QUESTION SECTION:
    ;domain.tld.                     IN      MX
    
    ;; AUTHORITY SECTION:
    domain.tld.              86400   IN      SOA     ns1.domain.com. ns2.domain.net. 2007032902 28800 7200 604800 86400
    
    ;; Query time: 0 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    

    The zone file looks like this:

    Code:
    $TTL        86400
    @       IN      SOA     ns1.domain.com. admin.domain.net. (
                            2007032902       ; serial, todays date + todays serial #
                            28800              ; refresh, seconds
                            7200              ; retry, seconds
                            604800              ; expire, seconds
                            86400 )            ; minimum, seconds
    ;
                    NS      ns1.domain.com.              ; Inet Address of name server 1
                    NS      ns2.domain.com.              ; Inet Address of name server 2
    ;
    
    www  MX      10 host.domain.com.
      MX      10 host.domain.com.
      MX      10 host.domain.com.
    
    domain.tld.      A        11.11.11.11
    sunrise       A       11.11.11.11
    smw       A       11.11.11.11
    www       A       11.11.11.11
    blog       A       11.11.11.11
    test       A       11.11.11.11
    
    First what's going on with those MX recors? They're double…

    Then… the syntax looks "strange".

    Shouldn' it look like this:

    Code:
    localhost               IN      A       11.11.11.11
    @                       IN      A       11.11.11.11
    www                     IN      A       11.11.11.11
    mail                    IN      A       11.11.11.11
    
    loopback                IN      CNAME   localhost
    smw                     IN      CNAME   www
    sunrise                    IN      CNAME   www
    blog                    IN      CNAME   www
    
    
    @                       IN      MX 10   mail
    
    The "IN" is missing…


    And… when I manually add somthing like this to my zonefile:

    Code:
    @                       IN      MX 10   www
    

    ...the query for MX returns correct results…

    Code:
    ;; QUESTION SECTION:
    ;domain.net.                     IN      MX
    
    ;; ANSWER SECTION:
    domain.net.              86400   IN      MX      10 www.domain.net.
    
    


    I just used the ISPconfig checkboxes in ISPmanager "create dns" and "create dns-mx"… I did nothing through the DNS Manager.
    And… when I take a look at the records in the DNS Manager I can't see any MX records there… and if I try to add one I get an error message saying that there's already one…

    Looks like a bug, hm?

    Best wishes
    Yves
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    The syntax of the ISPConfig bind file is ok.

    I'am pretty sure that they are ther, please check again.

    I dont think so. Please check if the domain or mx record is in the recycle bin.
     
  3. DOCK

    DOCK New Member

    Hi,

    the recycle bin is empty.
    Please tell me why I can't dig the MX record with the ISPconfig syntax.
    When I manually add a MX record in the recommended syntax (like it's shown in the bind manual…) I can ´dig´ it correctly.

    Here are some screenshots…
     

    Attached Files:

  4. DOCK

    DOCK New Member

    One more… (Fill: The message you have entered is too short. Please lengthen your message to at least 10 characters.)
     

    Attached Files:

  5. till

    till Super Moderator Staff Member ISPConfig Developer

    Please delete the duplicate MX record in the DNS-manager.
     
  6. DOCK

    DOCK New Member

    OK. Now I get correct dig results.
    But… why could this happen?
     
    Last edited: Mar 30, 2007
  7. till

    till Super Moderator Staff Member ISPConfig Developer

    I'am not sure. Normally ISPConfig is checking for duplicates. I will have a look at the code, maybe there are some situations where the check does not work properly. You are using the latest stable release?
     
  8. DOCK

    DOCK New Member

    Yes, I'm using the latest stable release.
    I'll send you a private message with my contact details - I'd like to grant you access to the server if it helps for your code revision.
     

Share This Page