From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 8D73221F25E for ; Tue, 25 Mar 2014 00:10:04 -0700 (PDT) Received: by mail-ie0-f179.google.com with SMTP id lx4so42535iec.38 for ; Tue, 25 Mar 2014 00:10:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=T/JCYDhYMJte76mUnp/nvGPljhknE0VHEq0hhf4fziQ=; b=0NZtxtXo+s2mxUCk/neRemKlR0OdIdvH8aerjD0eWSVMIClQS9Xnzgd14H11r8b9oY 1SRavbZEVwt7GabD3UbBbQrKtP9ISzc2DxYkwiLWwdW3GPGqV1bN31bIwREbXUamqBzQ spKXlylLWlrIe+LbSSaRKOPTCVP1BeYWRx2LIUxyvVhIMGr38SOg6YCYJmQ/TzoxkZ2F M9NwXHKPeelgepa909aV+rB1R2ENVDfBl9bXtHma9/r7q6Ksd2Ks6mvypu6ZXsuKeeEu IswTInztKqVmZFS+7TFCMyOsUlCaSTeEjaB8eKBBtU49Bm3ufA14drXfqqUsWqKyYywy PRYQ== MIME-Version: 1.0 X-Received: by 10.50.109.130 with SMTP id hs2mr15646555igb.29.1395731403690; Tue, 25 Mar 2014 00:10:03 -0700 (PDT) Received: by 10.64.238.70 with HTTP; Tue, 25 Mar 2014 00:10:03 -0700 (PDT) Date: Tue, 25 Mar 2014 08:10:03 +0100 Message-ID: From: Aaron Wood To: cerowrt-devel Content-Type: multipart/alternative; boundary=089e0111bc9a84d81b04f5690a31 Subject: [Cerowrt-devel] 3.10.32-12: very nice, but odd dns requests X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Mar 2014 07:10:04 -0000 --089e0111bc9a84d81b04f5690a31 Content-Type: text/plain; charset=ISO-8859-1 Yesterday, I upgraded to 3.10.32-12 (rrul results coming soon, it's a big improvement over 3.10.24-8, though I'm not sure why, exactly). This morning I turned on dns request logging, since I wanted to keep a better eye on the dnssec results (and so that I had some short-term forensic trails in case things were failing). I'm seeing the following in the dns request logs, every 5 seconds: Tue Mar 25 08:03:50 2014 daemon.info dnsmasq[30169]: query[AAAA] loopback from 127.0.0.1 Tue Mar 25 08:03:50 2014 daemon.info dnsmasq[30169]: config loopback is NODATA-IPv6 Tue Mar 25 08:03:50 2014 daemon.info dnsmasq[30169]: query[A] loopback from 127.0.0.1 Tue Mar 25 08:03:50 2014 daemon.info dnsmasq[30169]: config loopback is NODATA-IPv4 Tue Mar 25 08:03:50 2014 daemon.info dnsmasq[30169]: query[AAAA] lan from 127.0.0.1 Tue Mar 25 08:03:50 2014 daemon.info dnsmasq[30169]: config lan is NODATA-IPv6 Tue Mar 25 08:03:50 2014 daemon.info dnsmasq[30169]: query[A] lan from 127.0.0.1 Tue Mar 25 08:03:50 2014 daemon.info dnsmasq[30169]: config lan is NODATA-IPv4 Tue Mar 25 08:03:55 2014 daemon.info dnsmasq[30169]: query[AAAA] loopback from 127.0.0.1 Tue Mar 25 08:03:55 2014 daemon.info dnsmasq[30169]: config loopback is NODATA-IPv6 Tue Mar 25 08:03:55 2014 daemon.info dnsmasq[30169]: query[A] loopback from 127.0.0.1 Tue Mar 25 08:03:55 2014 daemon.info dnsmasq[30169]: config loopback is NODATA-IPv4 Tue Mar 25 08:03:55 2014 daemon.info dnsmasq[30169]: query[AAAA] lan from 127.0.0.1 Tue Mar 25 08:03:55 2014 daemon.info dnsmasq[30169]: config lan is NODATA-IPv6 Tue Mar 25 08:03:55 2014 daemon.info dnsmasq[30169]: query[A] lan from 127.0.0.1 Tue Mar 25 08:03:55 2014 daemon.info dnsmasq[30169]: config lan is NODATA-IPv4 Tue Mar 25 08:04:00 2014 daemon.info dnsmasq[30169]: query[AAAA] loopback from 127.0.0.1 Tue Mar 25 08:04:00 2014 daemon.info dnsmasq[30169]: config loopback is NODATA-IPv6 Tue Mar 25 08:04:00 2014 daemon.info dnsmasq[30169]: query[A] loopback from 127.0.0.1 Tue Mar 25 08:04:00 2014 daemon.info dnsmasq[30169]: config loopback is NODATA-IPv4 Tue Mar 25 08:04:00 2014 daemon.info dnsmasq[30169]: query[AAAA] lan from 127.0.0.1 Tue Mar 25 08:04:00 2014 daemon.info dnsmasq[30169]: config lan is NODATA-IPv6 Tue Mar 25 08:04:00 2014 daemon.info dnsmasq[30169]: query[A] lan from 127.0.0.1 Tue Mar 25 08:04:00 2014 daemon.info dnsmasq[30169]: config lan is NODATA-IPv4 Anyone have any ideas as to what's looking up "lan" and "loopback" this often? Thanks, -Aaron --089e0111bc9a84d81b04f5690a31 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Yesterday, I upgraded to 3.10.32-12 (rrul results coming s= oon, it's a big improvement over 3.10.24-8, though I'm not sure why= , exactly).

This morning I turned on dns request logging= , since I wanted to keep a better eye on the dnssec results (and so that I = had some short-term forensic trails in case things were failing).

I'm seeing the following in the dns request logs, e= very 5 seconds:

Tue Mar 25 08:03:50 2014 daemon.info dnsmasq[30169]: query[AAAA] loop= back from 127.0.0.1
Tue Mar 25 08:03= :50 2014 daemon.info dnsmasq[30169]: que= ry[A] loopback from 127.0.0.1
Tue Mar 25 08:03= :50 2014 daemon.info dnsmasq[30169]: que= ry[AAAA] lan from 127.0.0.1
Tue Mar 25 08:03:50 2= 014 daemon.info dnsmasq[30169]: query[A]= lan from 127.0.0.1
Tue Mar 25 08:03:55 2= 014 daemon.info dnsmasq[30169]: query[AA= AA] loopback from 127.0.0.1
Tue Mar 25 08:03= :55 2014 daemon.info dnsmasq[30169]: que= ry[A] loopback from 127.0.0.1
Tue Mar 25 08:03= :55 2014 daemon.info dnsmasq[30169]: que= ry[AAAA] lan from 127.0.0.1
Tue Mar 25 08:03:55 2= 014 daemon.info dnsmasq[30169]: query[A]= lan from 127.0.0.1
Tue Mar 25 08:04:00 2= 014 daemon.info dnsmasq[30169]: query[AA= AA] loopback from 127.0.0.1
Tue Mar 25 08:04= :00 2014 daemon.info dnsmasq[30169]: que= ry[A] loopback from 127.0.0.1
Tue Mar 25 08:04= :00 2014 daemon.info dnsmasq[30169]: que= ry[AAAA] lan from 127.0.0.1
Tue Mar 25 08:04:00 2= 014 daemon.info dnsmasq[30169]: query[A]= lan from 127.0.0.1


Thanks,
-Aaron
--089e0111bc9a84d81b04f5690a31--