reload force?

[phn at icke-reklam.ipsec.nu]

Dave Ellenberger <removethis-dave at nofuture.ch> wrote:
> Hi

> First sorry for my poor english. I hope I can explain my problem
> good/clearly enough.

> I was using BIND 8.x so far on our secondary DNS servers. Sometimes it
> happened that some customer made a typo in the serial.. e.g. 200209120 (one
> zero to much). When this happend I just deleted the zone file (rm
> db.mydomain.com) on the secondary DNS and hit "ndc reload". BIND8 did a new
> AXFR and loaded the zone from primary without any problems. The problem was
> solved.

> Now on BIND 9.x when I delete the file and hit "rndc reload mydomain.com" I
> get the following error:

> ->    named[27383]: zone mydomain.com/IN: refresh: could not set file
> modification time of 'db.mydomain.com': file not found

> However, BIND 9 only does a new AXFR when I reload the whole server. But
> this server has ~2000 domains in named.conf. So the named process needs
> about 7-8 seconds to shutdown and about 5 seconds to load all zones. Thats
> why restart is a really bad solution for this problem.

> OK, so I changed the serial on secondary server and putted in serial (e.g.
> 1) to force the secondary to reload the zone from the primary with lower
> number than it was before. This worked, but it also is a bad solution.

> What is your solution to force a secondary to load a zone with lower serial
> than the current zone?

There is a nice solution mentioned in "managing dns and bind" ( the book).

basicallyu it wraps the serial, ignoring overflow of the 32bit number.


See : "http://www.acmebw.com/askmrdns/archive.php?category=83&question=616"
for details.

> Dave




-- 
Peter Håkanson         
        IPSec  Sverige      ( At Gothenburg Riverside )
           Sorry about my e-mail address, but i'm trying to keep spam out,
	   remove "icke-reklam" if you feel for mailing me. Thanx.