DNS resync / mirror problem.

[DKLeader]

Hi,

Everything has been working fine or thats what I thought.
I needed to renew one of my name servers. I switched it off thinking that one of the others (have 3 in all) would take over. All domains went "offline".
In ISPConfig ns2 and ns3 are mirrors of ns1. I am running version 3.0.4.5

Below zone is from one of my domains :
On ns1 :

$TTL        3600
@       IN      SOA     ns1.superweb.dk. admin.superweb.dk. (
                        2012060107       ; serial, todays date + todays serial #
                        3600              ; refresh, seconds
                        3600              ; retry, seconds
                        3600              ; expire, seconds
                        3600 )            ; minimum, seconds
;

coolride.dk. 3600      NS        ns1.superweb.dk.
coolride.dk. 3600      NS        ns2.superweb.dk.
coolride.dk. 3600      NS        ns3.superweb.dk.

On ns2:

$TTL        3600
@       IN      SOA     ns1.superweb.dk. admin.superweb.dk. (
                        2012060107       ; serial, todays date + todays serial #
                        3600              ; refresh, seconds
                        3600              ; retry, seconds
                        3600              ; expire, seconds
                        3600 )            ; minimum, seconds
;

coolride.dk. 3600 A        92.62.196.69
coolride.dk. 3600      MX    15   coolride.dk.
coolride.dk. 3600      MX    10   mail.coolride.dk.
coolride.dk. 3600      NS        ns1.superweb.dk.
coolride.dk. 3600      NS        ns2.superweb.dk.
coolride.dk. 3600      NS        ns3.superweb.dk.
ftp.coolride.dk. 3600      CNAME        coolride.dk.
mail.coolride.dk. 3600 A        92.62.196.69
www.coolride.dk. 3600      CNAME        coolride.dk.

And on ns3 :

$TTL        3600
@       IN      SOA     ns1.superweb.dk. admin.superweb.dk. (
                        2012060107       ; serial, todays date + todays serial #
                        3600              ; refresh, seconds
                        3600              ; retry, seconds
                        3600              ; expire, seconds
                        3600 )            ; minimum, seconds
;

coolride.dk. 3600      NS        ns1.superweb.dk.
coolride.dk. 3600      NS        ns2.superweb.dk.
coolride.dk. 3600      NS        ns3.superweb.dk.

I have tried using the resync function and can see that all 3 are increased in serial.
I can connect to the master database from all 3 name servers.
Any suggestions?

[DKLeader]

From dig @localhost coolride.dk
On NS1 :

; <<>> DiG 9.6-ESV-R4 <<>> @localhost coolride.dk
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8703
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

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

;; AUTHORITY SECTION:
coolride.dk.            3600    IN      SOA     ns1.superweb.dk. admin.superweb.dk. 2012060107 3600 3600 3600 3600

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Jun  1 20:15:02 2012
;; MSG SIZE  rcvd: 84

ON NS2 :

; <<>> DiG 9.6-ESV-R4 <<>> @localhost coolride.dk
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16214
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3

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

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

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

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

;; Query time: 3 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Jun  1 20:21:33 2012
;; MSG SIZE  rcvd: 156

On NS3 :

; <<>> DiG 9.7.3 <<>> @localhost coolride.dk
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35248
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

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

;; AUTHORITY SECTION:
coolride.dk.            3600    IN      SOA     ns1.superweb.dk. admin.superweb.dk. 2012060107 3600 3600 3600 3600

;; Query time: 0 msec
;; SERVER: ::1#53(::1)
;; WHEN: Fri Jun  1 20:18:42 2012
;; MSG SIZE  rcvd: 84

[falko]

Please check your syslog for named errors on all three nodes.

[DKLeader]

No errors related to that domain (edit)

I know that the serial in below is different that my previous sent, but tried a few things without luck. Zones are still the same but with new serial.
From NS1 :

Jun 2 10:57:05 ns1 named[6860]: zone coolride.dk/IN: loaded serial 2012060201
Jun 2 10:57:05 ns1 named[6860]: zone coolride.dk/IN: sending notifies (serial 2012060201)

NS2

Jun 2 11:03:09 ns2 named[1927]: zone coolride.dk/IN: loaded serial 2012060201
Jun 2 11:03:09 ns2 named[1927]: zone coolride.dk/IN: sending notifies (serial 2012060201)
.
.
Jun 2 11:03:10 ns2 named[1927]: client 192.168.100.1#38473: received notify for zone 'coolride.dk'

NS3

Jun 2 11:03:06 ns3 named[3458]: zone coolride.dk/IN: loaded serial 2012060201
Jun 2 11:03:06 ns3 named[3458]: zone coolride.dk/IN: sending notifies (serial 2012060201)
.
.
Jun 2 11:03:11 ns3 named[3458]: client 192.168.100.1#19685: received notify for zone 'coolride.dk'

Errors seen for other domains, but this is only in the syslog on NS1:

Jun 2 10:51:12 ns1 named[6860]: zone dkleader.dk/IN: has no NS records
Jun 2 10:51:12 ns1 named[6860]: zone dkleader.dk/IN: not loaded due to errors.

[DKLeader]

Just tried deleting DNS for Coolride and created it again.
Then it was created on all 3 name servers.
Do I then have to do this for all my domains? Got more than 50.

And why did they suddenly loose part of the information and why can't it resync all information?

[falko]

Not sure what happened, but to me it looks as if you had a faulty master zone:

Jun 2 10:51:12 ns1 named[6860]: zone dkleader.dk/IN: has no NS records
Jun 2 10:51:12 ns1 named[6860]: zone dkleader.dk/IN: not loaded due to errors.

[DKLeader]

But it wasn't the only domain with that fault. More or less all .dk domains on my server had that problem.

Problem was solved by saving all lines in each zone through ISPConfig. Took some time to do.

It has been running for 24 hours now without any problems and I have replaced one of the name servers followed by a resync.