From owner-freebsd-questions@freebsd.org Tue Sep 6 13:27:18 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F767BC44F1 for ; Tue, 6 Sep 2016 13:27:18 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from smtp.krpservers.com (smtp.krpservers.com [62.13.128.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.krpservers.com", Issuer "RapidSSL SHA256 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0CA8CB2F for ; Tue, 6 Sep 2016 13:27:17 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213] (may be forged)) (authenticated bits=0) by smtp.krpservers.com (8.15.2/8.15.2) with ESMTPSA id u86DREA2051366 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Sep 2016 14:27:15 +0100 (BST) (envelope-from kpielorz_lst@tdx.co.uk) Date: Tue, 06 Sep 2016 14:27:02 +0100 From: Karl Pielorz To: Cristiano Deana cc: freebsd-questions@freebsd.org Subject: Re: Query re. /etc/resolv.conf... Message-ID: X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; FORMAT=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Sep 2016 13:27:18 -0000 --On 06 September 2016 14:33 +0200 Cristiano Deana wrote: > Did you actually check what is really going on? Eg: > tcpdump -ni your_interface port 53 > > Just to verify which DNS is trying to reach, timeout, etc. Ok, having run some more tests on here - it appears it may be Xen (virtualisation) related. I had forgotten the 10.3 box I was testing on was a virtual machine. It appears the same test on a 'real' 10.3 box succeeds (as it does on the 9.x boxes). However, a virtual XenServer FreeBSD 10.3 instance has the problem... I'll kick it over to -xen to see if anyone there can think of anything... Incase anyone else encounters the issue - as a work around removing everything bar '127.0.0.1' in '/etc/resolv.conf' does work - i.e. Unbound will correctly pool the forwards you set it up for - if one disappears, name resolution continues. Very strange... Thanks to all who replied, -Karl