From owner-freebsd-questions@freebsd.org Tue Jan 30 19:45:25 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 38801EDE89F for ; Tue, 30 Jan 2018 19:45:25 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C2BC37DAC9 for ; Tue, 30 Jan 2018 19:45:24 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 8388BEDE89E; Tue, 30 Jan 2018 19:45:24 +0000 (UTC) Delivered-To: questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4937EEDE89D for ; Tue, 30 Jan 2018 19:45:24 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DDCB07DAC7 for ; Tue, 30 Jan 2018 19:45:23 +0000 (UTC) (envelope-from odhiambo@gmail.com) Received: by mail-oi0-x22f.google.com with SMTP id c189so8011897oib.12 for ; Tue, 30 Jan 2018 11:45:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=/Rh7MTZazD0o5HtKeTzvJMlGvtv8LUzKRMfs9N3ppSY=; b=V3BkdSiZrw4Njv6IZ9rN4wJFkIDlvSiGHYb/uVRyP9LA9JfF+7G768/3d9bf5Yk2rE aAMGqqIRL30UNHoWMqzKDEXYaWpVzdK0ls9wJV5VSmlgSN8pdnrYfJIap+s6IJOv6Lsw OqshYv1nJScLz5QNnSW092JMhPzZ4OUK3kv8SMrt6DNkRAf5ACsARaGy21nevtrSLAIq UlucZvPuQyU0Recn/HxTx/ofyTu4QvNtJc9qJC2cBEMy1J7MZ2mxjhD8JlCyDlBCGIWQ 0hcMYYIEruAaIhX08jRkcAuS4RZ6/cS2wQF+vYVXD0JXqYuj3d+RIb381vt8g7ffPKY8 daVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=/Rh7MTZazD0o5HtKeTzvJMlGvtv8LUzKRMfs9N3ppSY=; b=bF1XoPdd9WtJQ1NcnnKZ126OqoWBjf8Cgwz/Fx73dk3zRbqIYvSS5vtR7bbPkk8jRj TxViqm2tbkwYLH21kcge5Ta08w1eeQPvx2cUDcpEM3eFhGFpGm/t0E9QU1mpOlw4Jdn7 gmCv7NRrYqi9V1xZyXFU+Fz/J9Vggs8JgHN6BDECmFpNz64Pg0m6gpN0QUpxuNvF6OVY hSaquRg+/E7zGLX8vamHjRXCN205NTR5klcibmsX/mk7VIwW7EyF6Fzm6K53GRFBo2hE Gp1wgOJ9QoUtEZlOVr7cGYBjn6Q9IJX6QlP7qLuwBSlbAYnVfwemo/e9S1oYhwumcQxD DgSg== X-Gm-Message-State: AKwxytcggQXbA0a0BzKEMjla8rLMHFNlwrQ0hM8x5QxamSeRa/RQFM7x TiMmtUO+NFNt0N9Nq5b7NwDL48i0fSkUgqcsGckLaA== X-Google-Smtp-Source: AH8x227DtG8YuzOx5hD+sxZoRR6dVK+Bp8aujZJa5YgdX7svQ7ImKPjJ8VKHfapCOKANilnX19dkD4fSaYYxpnY48ew= X-Received: by 10.202.175.207 with SMTP id y198mr20337414oie.213.1517341522577; Tue, 30 Jan 2018 11:45:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.13.9 with HTTP; Tue, 30 Jan 2018 11:44:42 -0800 (PST) From: Odhiambo Washington Date: Tue, 30 Jan 2018 22:44:42 +0300 Message-ID: Subject: Re: Strange Name Server Problem - SOLVED To: questions Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 19:45:25 -0000 On 20 April 2017 at 21:48, Odhiambo Washington wrote: > I have a server running FreeBSD 11.0-STABLE. > > I am a little stumped why my local caching bind instance doesn't answer > queries. I have then opted to run bind on port 5353 and unbound on port 53. > I still experience the same problem! > > root@waridi:/usr/local/etc/unbound # sockstat -l | grep named > bind named 50877 20 tcp4 192.168.27.254:5353 *:* > bind named 50877 21 tcp4 127.0.0.1:5353 *:* > bind named 50877 22 tcp4 127.0.0.1:953 *:* > bind named 50877 23 tcp6 ::1:953 *:* > bind named 50877 512 udp4 192.168.27.254:5353 *:* > bind named 50877 513 udp4 192.168.27.254:5353 *:* > bind named 50877 514 udp4 192.168.27.254:5353 *:* > bind named 50877 515 udp4 127.0.0.1:5353 *:* > bind named 50877 516 udp4 127.0.0.1:5353 *:* > bind named 50877 517 udp4 127.0.0.1:5353 *:* > root@waridi:/usr/local/etc/unbound # sockstat -l | grep unb > unbound unbound 51296 3 udp4 127.0.0.1:53 *:* > unbound unbound 51296 4 tcp4 127.0.0.1:53 *:* > unbound unbound 51296 5 udp4 192.168.27.254:53 *:* > unbound unbound 51296 6 tcp4 192.168.27.254:53 *:* > unbound unbound 51296 10 udp4 *:29712 *:* > unbound unbound 51296 11 udp4 *:28511 *:* > unbound unbound 51296 13 udp4 *:35511 *:* > unbound unbound 51296 14 udp4 *:19644 *:* > unbound unbound 51296 15 udp4 *:22549 *:* > unbound unbound 51296 16 udp4 *:30714 *:* > unbound unbound 51296 17 udp4 *:11907 *:* > unbound unbound 51296 18 udp4 *:50834 *:* > root@waridi:/usr/local/etc/unbound # > > Name resolution takes so long because it has to happen via the ISPs DNS > Servers, which are the 3rd and 4th options in /etc/resolv.conf > > I am actually lost as to where to start looking. > It turns out that bind was trying to resolve the names against IPv6 addresses. It's only today (20180130) that I figured this out by running nslookup and looking at what bind was logging. I installed bind-9.11 with IPv6 disabled and now my name lookups is fast! As I had wanted. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft."