Re: Bind 9 resolver timeout and ncache behaviour

2 msg	still having one email problem
2 msg	inability to send email - who's problem?
6 msg	problems sending email to various domains
2 msg	Secondary slave DNS not replicate zone files.
2 msg	Memory
2 msg	RR's
5 msg	Multiple PTRs for the same IP
2 msg	Question about the Two Recent Security Bulletins
3 msg	BIND 9.3.3rc3 can't load the config?
17 msg	Problem with DNS on mandriva 2007

Bind 9 resolver timeout and ncache behaviour
\ Nick Garfield (25 Jan 2007)
. \ Stefan Puiu (28 Jan 2007)
. \ Barry Margolin (28 Jan 2007)

4 msg	Q: DNS query format
5 msg	bind 9.3
4 msg	BIND 9.5?
8 msg	BIND 9 Memory Leak?
4 msg	setting up round robin
1 msg	post test
3 msg	Records
2 msg	help with DNS cache
4 msg	logging config no longer working as expected

Subject:	Re: Bind 9 resolver timeout and ncache behaviour
Group:	Bind-users
From:	Barry Margolin
Date:	28 Jan 2007

In article <epic1e$1bp2$1>,
"Stefan Puiu" <stefan.puiu> wrote:

> > (4) The client's resolver probably has a longer timeout than the caching
> > named. When the caching named has a timeout what does the caching named
> > return to the client's resolver - nothing or an error message?

> Regarding 4, I guess that's also easy to try - however, it's not a
> rule that the stub resolver times out last, sometimes it can time out
> before BIND. When BIND times out first, I would expect an NXDOMAIN
> answer to be sent.

I would expect SERVERR. NXDOMAIN should only be returned when an
authoritative server (or a forwarder that you're proxying through)
returns an NXDOMAIN code.

--
Barry Margolin, barmar
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 ***