Trouble with Slave-Updates

André Höpner andre at hoepner.net
Thu Aug 12 11:55:23 UTC 2004


Hello bind-users,

we have two nameservers for about 120 domains. both ar running
bind 9.23. one is primary and one is secondary.
after starting both servers all is running fine.

after a few days, when mot of the zones expires, the secondary
does the log-entry about expiration, but it seems, that he does not
update the zones after that. some time later the secondary gives
no answer about the expired zones.

i must stop and start the primary server. that sends notifies and
only after recieving this notifies the secondary updates the zones.

is that ok? i think not. should i restart the primary server every day
to prevent the expiration? i hope not.
how can i fix this?

please help. im not sure if i made anything wrong... :-(
best regardings
andre


for debugging here some info:

--- example-zone ---
@       IN      SOA     ns.server1.net.       hostmaster.server1.net. (
                        2004081201
                        8H
                        2H
                        1W
                        1D )

                NS      ns.server1.net.               ; 1. nameserver
                NS      ns.server2.net.                  ; 2. nameserver

                MX      10 mail.server3.net.          ; 1. mailserver

example-domain.net.           A       123.123.123.123

www                     A       123.123.123.123
ftp                     A       123.123.123.123


--- primary-entry ---
zone "example-domain.net" {
        type master;
        allow-query { any; };
        file "zones/example-domain.net";
};


--- slave-entry ---
zone "example-domain.net" in {
  type slave;
  masters { ip_of_server1.net; };
  file "slave_cache/example-domain.net";
};




More information about the bind-users mailing list