Secondary updates on bind 8.1.2 solaris 7 X86

S0LARlSTEK at aol.com S0LARlSTEK at aol.com
Sat Oct 30 20:35:46 UTC 1999


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.

Greg

<< It looks my secondary name server had a core dump of over 233 mega bytes.  
Is 
 there any particular reason this would happen.  I am running bind 8.1.2 as 
 default in solaris 7 X86.
 
 Greg
 
 In a message dated 10/28/99 9:14:24 AM Pacific Daylight Time, 
 barmar at bbnplanet.com writes:
 
 << In article <199910280539.PAA20810 at bsdi.dv.isc.org>,
   <Mark_Andrews at iengines.com> wrote:
  >  Stop the master nameserver and restart it, then look at every
  >  message logged between starting and Ready to answer queries.
  >  You will have errors in the zone files.
  
  I suspect not.  I was able to get a zone transfer from his primary with no
  problem, so it seems like his slave should as well.
  
  % dig networkamerica.org axfr @ns1.websgt.net
  
  ; <<>> DiG 2.2 <<>> networkamerica.org axfr @ns1.websgt.net 
  ; (1 server found)
  networkamerica.org.    86400   SOA ns1.websgt.net. webmaster.websgt.net. (
             1999101500  ; serial
             28800   ; refresh (8 hours)
             3600    ; retry (1 hour)
             604800  ; expire (7 days)
             86400 ) ; minimum (1 day)
  networkamerica.org.    86400   NS  ns1.websgt.net.
  networkamerica.org.    86400   NS  ns2.jtinternet.com.
  networkamerica.org.    86400   MX  10 web60.websgt.net.
  networkamerica.org.    86400   A   216.32.58.8
  localhost.networkamerica.org.  86400   A   127.0.0.1
  www.networkamerica.org.    86400   A   216.32.58.8
  networkamerica.org.    86400   SOA ns1.websgt.net. webmaster.websgt.net. (
             1999101500  ; serial
             28800   ; refresh (8 hours)
             3600    ; retry (1 hour)
             604800  ; expire (7 days)
             86400 ) ; minimum (1 day)
  ;; Received 8 answers (8 records).
  ;; FROM: tools to SERVER: 216.32.58.6
  ;; WHEN: Thu Oct 28 11:47:11 1999
  
  Try running named-xfer with debugging and tracing enabled:
  
  named-xfer -z networkamerica.org -f /tmp/xfer.db -s 0 -d 3 -l /tmp/xfer.log 
 216.32.58.6
  
  This will create a file /tmp/xfer.log.<randomness> that contains the
  debugging information.
  
  -- 
  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.
  
  
   >>
  >>


More information about the bind-users mailing list