Bind as slave gets corrupted zone files

Discussion in 'Installation/Configuration' started by JPascalTaipei, Apr 14, 2015.

  1. JPascalTaipei

    JPascalTaipei New Member

    Hello,

    I have 2 ISPConfig servers running:
    - an old 3.0.4.6 that I use as the primary DNS
    - a new 3.0.5.4 that I used as a slave DNS.

    I can add secondary DNS zone on the new 3.0.5.4 server. I had to modify the access right of /etc/bind/slave for it to be able to create its zone files.

    But I get strange zone files:
    Code:
    U,n:j  domaincomBnsdomaincomsuppordomaincomw▒▒-  :▒Q▒T  
    etc...
    
    Do you have any idea where is that coming from?

    Cheers,

    JP.
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    You can not use different ispconfig versions in a cluster, all nodes of a multiserver setup must use the same ispconfig version. You have to update the old server so that it runs the exact same release then the new one.
     
  3. JPascalTaipei

    JPascalTaipei New Member

    Thanks a lot for your answer Till.

    I actually understood that these zone files look strange because they are in raw format. They are perfectly fine. The synchronization between 3.0.4.6 as a master and 3.0.5.4 works apparently fine.

    Cheers!
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    you will get problems sooner or later which will break your database. you should really update both servers to the same version before it gets broken.
     
  5. JPascalTaipei

    JPascalTaipei New Member

    I will. Thank you very much for your feedback.
     

Share This Page