Return to BSD News archive
#! rnews 1563 sserve.cc.adfa.oz.au Path: sserve!newshost.anu.edu.au!munnari.oz.au!yoyo.aarnet.edu.au!harbinger.cc.monash.edu.au!msunews!caen!spool.mu.edu!howland.reston.ans.net!news.cac.psu.edu!news.pop.psu.edu!ra.nrl.navy.mil!elvis.cmf.nrl.navy.mil!not-for-mail From: kenh@cmf.nrl.navy.mil (Ken Hornstein) Newsgroups: comp.unix.bsd.netbsd.misc Subject: Re: named problem on netbsd 386? Date: 22 May 1995 14:48:20 -0400 Organization: Naval Research Lab, Connection Machine Facility Lines: 22 Message-ID: <3pqm9k$1fd@elvis.cmf.nrl.navy.mil> References: <D8qD44.K6I@daver.bungi.com> NNTP-Posting-Host: elvis.cmf.nrl.navy.mil In article <D8qD44.K6I@daver.bungi.com>, Dave Rand <dlr@daver.bungi.com> wrote: > >I'm having a strange problem with named on netbsd. > >Running as a secondary, it properly copies the zone information from the >master, and creates a file in /etc/namedb as you would expect. > >But the zone information does not appear to ever be refreshed! Changing the >serial number on the master, and using kill -HUP allows the new information >to be seen with nslookup, but only when setting the nameserver to the master. > >kill -HUP to the secondary named has no effect. Stopping and restarting >named has no effect. One must delete the zone copy in the /etc/namedb >directory in order for things to work again! > >Any ideas? I did pick up and compile the -current version last night. >Before I hack, has anyone else seen this? Am I just an idiot? This has worked fine under 1.0 for me for a long time. I am assuming that you are _incrementing_ the serial number, right? --Ken