From owner-freebsd-questions@freebsd.org  Mon Aug 31 13:51:18 2015
Return-Path: <owner-freebsd-questions@freebsd.org>
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 352489C6DDD
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Mon, 31 Aug 2015 13:51:18 +0000 (UTC) (envelope-from ml@my.gd)
Received: from mail-la0-f43.google.com (mail-la0-f43.google.com
 [209.85.215.43])
 (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 BCFEC1DF3
 for <freebsd-questions@freebsd.org>; Mon, 31 Aug 2015 13:51:17 +0000 (UTC)
 (envelope-from ml@my.gd)
Received: by labnh1 with SMTP id nh1so46491466lab.3
 for <freebsd-questions@freebsd.org>; Mon, 31 Aug 2015 06:51:09 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:date:message-id:subject:from:to
 :content-type;
 bh=eBxd2iLFqG93aFAujSwyDsZuGQl4c8qO0iWjMTdiirs=;
 b=kciQ4Kf8c2bkVENJNCBMbP5mqFHBm6vjNj0AMpo1miW+TJx6Bc8VTkA96D9/usAIZd
 tP54Ta+o/0bTVcej4dbueAVfUhbS5ig5d74CDCzI9d9puvMz8vjIqS/c1W74ZxRcMwwG
 5JZQ0CWclP34xRDc4wfVOhJYOnleLthwcwE34d5YSfBV2yLTwayaBQ9g12RQFeDZzHuP
 904QYrF742pcuAXa/DWvRWtPi9MR3z6yTDisuguMWvmdF8XCIgk4r91EuG0o0znr/XVq
 qacEIoxCo6jRmczwvL96hxm2dAL83PcEye3iM/S1wNtD+ojKO6IaBWWGMNQTClfmE/c1
 3Hxw==
X-Gm-Message-State: ALoCoQl8PGaWKjy97UxzcmyI5jMI7nZcNiW1dM86JAnia3eIj1Skay5sFEmdBfIUJedEsnoJl5tu
MIME-Version: 1.0
X-Received: by 10.152.170.130 with SMTP id am2mr10408770lac.54.1441029069167; 
 Mon, 31 Aug 2015 06:51:09 -0700 (PDT)
Received: by 10.112.60.34 with HTTP; Mon, 31 Aug 2015 06:51:09 -0700 (PDT)
Date: Mon, 31 Aug 2015 15:51:09 +0200
Message-ID: <CAE63ME44OfwDzj05TmmrYBLzLrvCW=DZ=0mo=8+y3wsX6JAHNQ@mail.gmail.com>
Subject: BIND - disabling IPv6 lookups
From: Damien Fleuriot <ml@my.gd>
To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.20
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Aug 2015 13:51:18 -0000

Hello list,


I'm currently experiencing this very weird behaviour with BIND 9.8.7
running on 10-STABLE and, obviously, installed from ports.


I'm trying to prevent BIND from trying to resolve AAAA resource records.

To this effect, I've added :
named_flags="-4" to /etc/rc.conf, as the man page and several google
searches suggest [1]


After restarting BIND, I see it's come back alive with the correct startup
flag :
/usr/local/sbin/named -4 -u bind -c /usr/local/etc/namedb/named.con


However, I still see queries for AAAA records :
13:39:26.990819 IP 10.104.10.252.54566 > 195.158[snip].53: 43577+ [1au]
AAAA? www.tvsembox.com. (45)

Is that expected behaviour ?
And yes, 10.104.10.252 is the actual FreeBSD box, not a client host trying
to resolve stuff.


[1]
https://www.sbarjatiya.com/notes_wiki/index.php/Disabling_IPv6_lookups_in_bind