Date: Wed, 19 Feb 2014 17:53:20 +0400 From: Dmitry Sivachenko <trtrmitya@gmail.com> To: Vitaly Magerya <vmagerya@gmail.com> Cc: stable@freebsd.org Subject: Re: options timeout in resolv.conf does not work in stable/10 Message-ID: <AA09D532-7F98-405C-A2CD-A8132FDF01A3@gmail.com> In-Reply-To: <5304B65C.1040500@gmail.com> References: <40E84CA7-E815-4B5E-AF0F-4B29C8B58186@gmail.com> <5304B65C.1040500@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19 =D1=84=D0=B5=D0=B2=D1=80. 2014 =D0=B3., at 17:49, Vitaly Magerya = <vmagerya@gmail.com> wrote: > Dmitry Sivachenko wrote: >> I have the following /etc/resolv.conf: >>=20 >> domain domain.my >> nameserver IP1 >> nameserver IP2 >> options timeout:1 >>=20 >>=20 >> On FreeBSD-9-STABLE, if IP1 is down, I get a dns response from IP2 = after 1 second. >> On FreeBSD-10, I get dns response from IP2 after 10 seconds. >>=20 >> I see no changes in resolv.conf(5) man-page about timeout parameter. >>=20 >> What am I missing? >=20 > Are you using host(1) command for this? I used drill(1), which probably also uses ldns and does not respect = optons? Also I noticed that drill(1) does not respect nameserver's order from = resolv.conf, and picks random one. Which is also strange and disappointing. > If so, host(1) in > 10-RELEASE does not respect 'options' from resolv.conf (there's > a note about this in it's man page); the system resolver (that > is, anything based on getaddrinfo(3)) should not be affected > though. >=20 > The reason for this regression is that host(1) is now based on > the ldns library, which doesn't currently parse the 'options' > directive (e.g. see [1]). >=20 > The solution is to add '-w 1' to the list of host(1) options. > Or to push the ldns folks to fix this. >=20 > [1] = http://git.nlnetlabs.nl/ldns/tree/resolver.c?id=3Df328ba0ccc3c0733d0451d50= 59b50e502206923a#n838
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AA09D532-7F98-405C-A2CD-A8132FDF01A3>