Secondary updates on bind 8.1.2 solaris 7 X86

[Barry Margolin]

In article <0.a8fa9285.254cb0a2 at aol.com>,  <S0LARlSTEK at aol.com> wrote:
>When I restart my secondary dns by running 
>
>"ps -ef | grep in.named"
>Then killing the process.  This is what I get in the messages logs.
>
>Oct 30 01:15:17 ns2 named[21314]: starting.  in.named BIND 8.1.2 Tue Oct  6 
>01:1
>3:12 PDT 1998
>Oct 30 01:15:17 ns2     Generic-5.7-October 1998
>Oct 30 01:15:17 ns2 named[21314]: cache.db: No such file or directory
>Oct 30 01:15:19 ns2 named[21315]: Ready to answer queries.
>Here I get some expired zones.
>Oct 30 01:20:30 ns2 named[21315]: attempted to fetch zone jtinternet.com from 
>se
>lf (216.32.58.7)
>
>For some odd reason I can't get the secondary to reproduce the cache.db file 
>or the jtinternet.com.db file.  jtinternet.com.db holds the zone information 
>for the secondary name server itself.  This is the strangest thing.

cache.db is not a file that the nameserver produces itself, you have to
install it manually.  It's the root server hints file that you can download
from <ftp://ftp.rs.internic.net/domain/named.root>.

The message about jtinternet.com says that you have the server configured
as a slave, with the master address being the machine's own address.  That
makes no sense.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.