On 12/08/2013 09:13, gevisz wrote: > The response of the first router contained an error that prevented all the > other applications to use it, the system knew about it (for example from > the output of the host utility) but, nevertheless did not proceeded with > the next router listed in resolv.conf. > > I do undersand that this may be because of the layered structure of the > networked software. But, nevertheless, I think that something is fundamentally > wrong with this.
What kind of error did you get? If complete garbage came back, I'm not sure what the resolver does with that (oddly enough, I never tested that) The more usual case is you get a proper DNS result of NXDOMAIN which indicates the query is valid, but the entry is not in DNS. It's pointless trying another cache as per DNS, they should all then return that result. This is why the router did not try the other entries in resolv.conf - that usually only happens when a cache does not respond. So the behaviour you saw is probably correct albeit not the behaviour you wanted. -- Alan McKinnon alan.mckin...@gmail.com
