DNS transfer to slave missing

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

  1. DKLeader

    DKLeader Member

    Hi,

    All servers I am running are physical servers.
    All are running on Debian Lenny.
    ISPConfig is version 3.0.3.1

    Have 2 nameservers (ns1.superweb.dk and ns2.superweb.dk) running fine in the setup. Decided to have an extra ns (ns3.superweb.dk) and got the permission from dk-hostmaster.dk (need a permission in Denmark to host .dk domains).
    I have used the installation guide "Installing A Multiserver Setup With Dedicated Web, Email, DNS And MySQL Database Servers On Debian 5.0 With ISPConfig 3" on "6 Installing The Secondary DNS Server" (believe it would be the same for a third DNS server).

    But the DNS zones are not copied to ns3.superweb.dk.

    If I do a
    Code:
    dig @ns1.superweb.dk superweb.dk
    I get
    Code:
    MainServer:/var/www/backups# dig @ns1.superweb.dk superweb.dk

; <<>> DiG 9.6-ESV-R3 <<>> @ns1.superweb.dk superweb.dk
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20149
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3

;; QUESTION SECTION:
;superweb.dk.                   IN      A

;; ANSWER SECTION:
superweb.dk.            3600    IN      A       92.62.196.69

;; AUTHORITY SECTION:
superweb.dk.            3600    IN      NS      ns1.superweb.dk.
superweb.dk.            3600    IN      NS      ns3.superweb.dk.
superweb.dk.            3600    IN      NS      ns2.superweb.dk.

;; ADDITIONAL SECTION:
ns1.superweb.dk.        3600    IN      A       92.62.196.66
ns2.superweb.dk.        3600    IN      A       92.62.196.67
ns3.superweb.dk.        3600    IN      A       92.62.196.77

;; Query time: 1 msec
;; SERVER: 92.62.196.66#53(92.62.196.66)
;; WHEN: Mon Jan 10 19:12:22 2011
;; MSG SIZE  rcvd: 147
    If I do a
    Code:
    dig @ns3.superweb.dk superweb.dk
    I get :
    Code:
    MainServer:/var/www/backups# dig @ns3.superweb.dk superweb.dk

; <<>> DiG 9.6-ESV-R3 <<>> @ns3.superweb.dk superweb.dk
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14983
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;superweb.dk.                   IN      A

;; AUTHORITY SECTION:
superweb.dk.            3600    IN      SOA     ns1.superweb.dk. admin.superweb.dk. 2011010608 3600 3600 1209600 3600

;; Query time: 1 msec
;; SERVER: 92.62.196.77#53(92.62.196.77)
;; WHEN: Mon Jan 10 19:12:33 2011
;; MSG SIZE  rcvd: 75
    On ns1.superweb.dk and ns2.superweb.dk the pri.superweb.dk looks like this :
    Code:
    $TTL        3600
@       IN      SOA     ns1.superweb.dk. admin.superweb.dk. (
                        2011010608       ; 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.
    On ns3.superweb.dk :
    Code:
    $TTL        3600
@       IN      SOA     ns1.superweb.dk. admin.superweb.dk. (
                        2011010608       ; 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
ns3.superweb.dk.      A        92.62.196.77
superweb.dk.      NS        ns3.superweb.dk.
    I waited 24 hours (1 hour should have been enough) and still same.

    I have about 10 domains on the server and the only 2 found on ns3 are superweb.dk and one other that I have changed.

    On the ISPCondig CP ns3.superrweb.dk is set as a mirror of ns1.superweb.dk and as a DNS Server in system.

    Anyone got a suggestion to what I have missed or done wrong?
     
    DKLeader, Jan 10, 2011
    #1
  2. Toucan

    Toucan Member

    I understand the slave needs to be set as mirror of the master to transfer dns records when using mydns. Although saying that, if I add a dns zone to the slave, it does seem to transfer to the master - so that's what I do!
     
    Toucan, Jan 10, 2011
    #2
  3. DKLeader

    DKLeader Member

    But it works between master and slave (ns2). It is only the transfer to slave (ns3) that is not performed.
     
    DKLeader, Jan 11, 2011
    #3
  4. Toucan

    Toucan Member

    I just remember Till mentioning the other week that mydns has issues with db replication and either mydns or SQL needs restarts - like yours mine transfers zones from ns5 to ns3 no problem but doesn't work ns3 to ns5.

    I'll be interested to see if you can resolve this
     
    Toucan, Jan 11, 2011
    #4
  5. DKLeader

    DKLeader Member

    I am using bind9.

    I have tested and there is no problen if I add a new domain. It seems only to be when an existing domains dns is edited. It only adds the new part to my latest dns server (ns3).
     
    DKLeader, Jan 11, 2011
    #5
  6. Toucan

    Toucan Member

    I think this is common to all ispconfig areas where a slave is added after the master. The slave only gets the new records as the master writes a new change. I doesn't do a complete db replication on setting up the slave. Previously I've gone through records and made a very small change on the master to force it to write the complete records to the slave db.

    However, as I understood it, mydns uses db replication but bind (which you say you're using) uses the secondary zone facility.

    Maybe someone else can give some better guidance.
     
    Toucan, Jan 11, 2011
    #6

Share This Page