Date: Thu, 20 Feb 2014 17:33:35 +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: <DA546629-6F07-45EF-B6A7-2958B3CEDD4F@gmail.com> In-Reply-To: <5304BADE.3040703@gmail.com> References: <40E84CA7-E815-4B5E-AF0F-4B29C8B58186@gmail.com> <5304B65C.1040500@gmail.com> <AA09D532-7F98-405C-A2CD-A8132FDF01A3@gmail.com> <5304BADE.3040703@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 18:08, Vitaly Magerya = <vmagerya@gmail.com> wrote: > Dmitry Sivachenko wrote: >>> Are you using host(1) command for this? >>=20 >> I used drill(1), which probably also uses ldns and does not respect = optons? >=20 > Yup. This is a sad regression. Now nagios checks could produce false = warnings if first nameserver is down because drill does not honor option timeout like most other programs :( >=20 >> 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. >=20 > There's a '-z' option to turn this off. >=20 Thanks. I have no idea why do they randomize it after all...=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DA546629-6F07-45EF-B6A7-2958B3CEDD4F>