the slave DS can't get refreshed!! why??????

WebReactor Networks bind at webreactor.net
Sun Mar 10 19:36:42 UTC 2002


Is this the entire contents of your zone file?  I noticed the distinct lack
of NS records.

What does named.conf look like on the master and slave?

Do you see anything in your logs on either server that relates to AXFR?

  - John R. S. 


> From: "lhzhou" <lhzhou at bj.cnuninet.net>
> Date: Sat, 9 Mar 2002 14:46:42 +0800
> To: <bind-users at isc.org>
> Subject: the slave DS can't get refreshed!! why??????
> 
> hello , everybody,
> who can tell me the possible reason of no-refreshing on slave NS???  Thanks.
> Such is my experience:
> here I have a primary NS and a slave NS, I keep the backup files on the slave
> NS of a certain zone. On master NS the original config is:
> 
> lnsy.cnuninet.net.hosts file:
> 
> @               IN      SOA     dns.lnsy.cnuninet.net.
> root.dns.lnsy.cnuninet.net. (
> 2002030603      ; Serial
> 10800           ; Refresh 3 hours
> 3600            ; Retry   1 hour
> 3600000         ; Expire  1000 hours
> 86400 )         ; Minimum 24 hours
> 
> 
> db1                     IN      A       211.93.80.60
> 
> Then after I changed the address of db1 to 211.93.80.203, and at the same time
> add the serial number, but after two days, my slave NS still can't get
> refreshed about the changes.   The cache file(named_dump.db) still contained
> the address of 211.93.80.60(I think it should be out of TTL ), and the backup
> file is unchanged too( I think it should refresh per 3 hours).
> Are there any other possiblity about the thing????
> Thank you for your help.
> 
> 
> 



More information about the bind-users mailing list