Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] 3.10.32-12: very nice, but odd dns requests
Date: Tue, 25 Mar 2014 08:10:03 +0100	[thread overview]
Message-ID: <CALQXh-PzTHkHkHyt8Qnsxw6bYSBEbLHTeAcpq1F+s1QoowcM_g@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2486 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 3735 bytes --]

                 reply	other threads:[~2014-03-25  7:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALQXh-PzTHkHkHyt8Qnsxw6bYSBEbLHTeAcpq1F+s1QoowcM_g@mail.gmail.com \
    --to=woody77@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox