Is this a mirror bug ?

Discussion in 'Installation/Configuration' started by DKLeader, Jan 17, 2011.

  1. DKLeader

    DKLeader New Member

    Hi,

    As I would understand it a mirror would be an exact copy. If one server crashes and needs re-install it would be able to replicate itself again once the server is back online.

    I have added a new nameserver (ns3) and sice I ticked that it should be a mirror of ns1 I would have expected it to hold the same zones after some period of time. My ns2 was installed together with ns1.

    All servers are physical and running Debian Lenny.
    ISPConfig vers : 3.0.3.2

    This is from ns1 (ns2 is the same) :
    Code:
    $TTL        3600
@       IN      SOA     ns1.superweb.dk. admin.superweb.dk. (
                        2011011701       ; serial, todays date + todays serial #
                        3600              ; refresh, seconds
                        3600              ; retry, seconds
                        1209600              ; expire, seconds
                        3600 )            ; minimum, seconds
;

cp.superweb.dk.      A        92.62.196.69
db1.superweb.dk.      A        92.62.196.66
db2.superweb.dk.      A        92.62.196.67
db3.superweb.dk.      A        92.62.196.69
db4.superweb.dk.      A        92.62.196.69
db5.superweb.dk.      A        92.62.196.70
db6.superweb.dk.      A        92.62.196.71
db7.superweb.dk.      A        92.62.196.72
db8.superweb.dk.      A        92.62.196.69
db9.superweb.dk.      A        92.62.196.69
ftp.superweb.dk.      CNAME        superweb.dk.
mail.superweb.dk.      A        92.62.196.69
ns1.superweb.dk.      A        92.62.196.66
ns2.superweb.dk.      A        92.62.196.67
ns3.superweb.dk.      A        92.62.196.77
superweb.dk.      A        92.62.196.69
superweb.dk.      MX    10   mail.superweb.dk.
superweb.dk.      MX    15   superweb.dk.
superweb.dk.      NS        ns1.superweb.dk.
superweb.dk.      NS        ns2.superweb.dk.
superweb.dk.      NS        ns3.superweb.dk.
www.superweb.dk.      CNAME        superweb.dk.
    and ns3 :
    Code:
    $TTL        3600
@       IN      SOA     ns1.superweb.dk. admin.superweb.dk. (
                        2011011701       ; serial, todays date + todays serial #
                        3600              ; refresh, seconds
                        3600              ; retry, seconds
                        1209600              ; expire, seconds
                        3600 )            ; minimum, seconds
;

cp.superweb.dk.      A        92.62.196.69
db9.superweb.dk.      A        92.62.196.69
mail.superweb.dk.      A        92.62.196.69
ns3.superweb.dk.      A        92.62.196.77
superweb.dk.      NS        ns3.superweb.dk.
    I might have asked this in one of my other threads, but cannot see that I received a clear answer to this :)
     
    DKLeader, Jan 17, 2011
    #1
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    There is a misunderstanding on your side regarding the mirror function. Mirroring means that all configuration changes get mirrored from the master to all slave servers. This means that every newly added domain get added to all mirrors and all changes on these domains or subrecords get mirrored too. It does not mean that domains that were added before you installed the server get mirrored.

    So there is no bug here. The problem with your setup is that you added a mirror server to a existing cluster that contained already records.

    If you want to resync dns records on all nodes of a cluster, you can use the dns resync tool which is available in svn and can be used also with the ispconfig stable versions. Download the ispconfig svn version and then copy the files:

    interface/web/tools/dns_resync.php
    interface/web/tools/templates/dns_resync.htm
    interface/web/tools/lib/menu.d/dns_resync.menu.php

    to the corresponding folders of your install on the master server. You will find a new menu item in the tools menu after you login again.
     
    till, Jan 17, 2011
    #2
  3. DKLeader

    DKLeader New Member

    Thanks for the clarification :)

    Downloaded the files and this solved my dns problem.
     
    DKLeader, Jan 17, 2011
    #3

Share This Page