secondary dns problem

Mark Andrews Mark_Andrews at isc.org
Wed Aug 9 05:50:40 UTC 2006


> well, the expire is set to 604800 on the primary dns.... I did notice while
> the primary dns was down the secondary continued to try and refresh the
> zones, I could see the timeouts in the syslog... is that whats causing it?

	The secondary trying to check if the copy of the zone it has
	is up to date.  If the primary is down there is nothing to
	answer the queries so they time out.  This is normal and does
	not impact on the secondary's ability to answer queries.

> On 8/9/06, Barry Margolin <barmar at alum.mit.edu> wrote:
> >
> > In article <ebbhp4$lra$1 at sf1.isc.org>,
> > "Stephen Vaughan" <stephenvaughan at gmail.com> wrote:
> >
> > > Hi,
> > > I have setup 2 nameservers using bind. One of them is acting as a
> > secondary
> > > dns and it transfers the zones from the primary. My problem is, when the
> > > primary dns server goes down I am unable to query the secondary dns. If
> > the
> > > primary dns server is up, I can query the secondary dns fine. Is there a
> > > special setting or something that I've missed?
> >
> > When you query the slave DNS "fine", does it return authoritative
> > responses?
> >
> > What is the expire time of the zone?  If it's too short, the zone may
> > expire on the slave server.
> >
> > >
> > > I can see the query attempt when looking at the logs in the secondary
> > dns,
> > > but the dig -t that I'm running on another server is timing out...
> >
> > --
> > Barry Margolin, barmar at alum.mit.edu
> > Arlington, MA
> > *** PLEASE post questions in newsgroups, not directly to me ***
> > *** PLEASE don't copy me on replies, I'll read them in the group ***
> >
> >
> >
> 
> 
> -- 
> Best Regards,
> Stephen
> 
> 
> 
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org



More information about the bind-users mailing list