Re: [Add] Home routers with their own DNS servers

Rob Sayre <sayrer@gmail.com> Sun, 18 August 2019 17:54 UTC

Return-Path: <sayrer@gmail.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8D24120121 for <add@ietfa.amsl.com>; Sun, 18 Aug 2019 10:54:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EF_fClXqoAll for <add@ietfa.amsl.com>; Sun, 18 Aug 2019 10:54:04 -0700 (PDT)
Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com [IPv6:2607:f8b0:4864:20::d36]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EAE9120059 for <add@ietf.org>; Sun, 18 Aug 2019 10:54:03 -0700 (PDT)
Received: by mail-io1-xd36.google.com with SMTP id j6so16006488ioa.5 for <add@ietf.org>; Sun, 18 Aug 2019 10:54:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=W0qdiyNGxMvIrCpNltVe203pQRpRbzJlgEecfUiZAZg=; b=KIaMVtnH876Vr9kaSuTrTT/Y4QhGn9UKJd2v+wweJBQ8V9hAOmyoCmcMiH/pKdsSek XCI50Y4Gf8I6ySJAiHDxsokR+1BVX4afz5VMzVEAMwqIKZ5lC9LqphO6e3CHH5snK/lo kY5vD3BbWQ6y9EUC8ka0+pfFF//ulxpa/VBXETntf7Txcy8QOpgh7UVZ3z56h0Z0NT/l KDPyyckBtZDkB+gm8y7B2Xbz73bgx4Kj5U3YN+tivskGxSOlkEiTsqtVgAFrfeGqkOLN pequ5Rth2n1nhPgymQ4CIsr9gR6RHRKPldGDeuyzO4oZ+PzRUZVY8DQO13kwD40oGiRR KfLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=W0qdiyNGxMvIrCpNltVe203pQRpRbzJlgEecfUiZAZg=; b=kpmzau5AyO9FHzRK49kF7PIO0ERvlz4cL/znLnITgRZILlUk08GrVa21Zli8n+c299 TjAQIV3ZMICCCr9+myCQvGHLYh3eKzx8Im/SeQG+MahpBuT5LHjqdJmu6UNoGO7sKsDC ezZUVtqKrMVeea7h99V6/LQQ7SqGgRS4xQF0TEPchl0CRrBne8hh8SYaGcI4t097dOUh zoAurNn7ozx+YSZHLDwm8k80wyaYCSaO8+neUNTd/NRNxTxNREN7cRz9kOEWyS4ZKsFd u9YPqGIwB++6jTJz/xgYzR8evyLvAw1ynejxgbPirZokiDFmVw2gl5mnTZswm9ncZclH MCsQ==
X-Gm-Message-State: APjAAAW5VMyqW5pMVHHurRfw9nlzXN8JxFDNoiMdv1MxZyEHToQmjJ6T 0D5STLkM31ZtZkp6+x8serR8ZubT7bVoaPYpBLRuJ+HUB2M=
X-Google-Smtp-Source: APXvYqxLIu4SAezvT/OF1gfVNYXNEKaHV05NOAbXb2a/P0RQBJtbx5e0MDg+lPEfp160b+Cb7uXAvThiQM3CB52rSRA=
X-Received: by 2002:a5d:9583:: with SMTP id a3mr21432926ioo.54.1566150841958; Sun, 18 Aug 2019 10:54:01 -0700 (PDT)
MIME-Version: 1.0
References: <CAChr6Sy9TeFLKAUYJ-XF7tjnwJokUVBjbkrTfQT0=F+a99ZT=g@mail.gmail.com>
In-Reply-To: <CAChr6Sy9TeFLKAUYJ-XF7tjnwJokUVBjbkrTfQT0=F+a99ZT=g@mail.gmail.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Sun, 18 Aug 2019 10:53:50 -0700
Message-ID: <CAChr6SwW+wVrHa2+FvEGda5xa266MvhJXOUm35p_JP5D4Lt4tg@mail.gmail.com>
To: ADD Mailing list <add@ietf.org>
Content-Type: multipart/mixed; boundary="00000000000099b41b059067e84c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/T8_-QJzzGicbUqqxNsqjpSCHVQY>
Subject: Re: [Add] Home routers with their own DNS servers
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Aug 2019 17:54:06 -0000

It looks like it uses some local telemetry to decide whether to use the
ISP's DNS servers.

I've attached a screenshot of its management application.

thanks,
Rob


On Sun, Aug 18, 2019 at 10:24 AM Rob Sayre <sayrer@gmail.com> wrote:

> Hi,
>
> I was reading the paper ekr recommended:
>
> <
> https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-liu_0.pdf
> >
>
> and I noticed they provide a service here:
>
> <http://whatismyresolver.com/>
>
> I ran this in Firefox with DoH. As expected, I got a result that indicated
> my resolver was Cloudflare.
>
> In other browsers, I found that my resolver was run by Google[1]. I was a
> little puzzled at first, since Google is not my ISP. But, then I remembered
> that my router is a Google Wifi product. I guess it uses its own DNS
> servers sometimes. I don't think it always does this, because I do
> occasionally see DNS redirect pages[2] from my ISP for NXDOMAIN responses,
> although I don't right now. Another possibility is that my ISP sometimes
> intercepts this traffic.
>
> I only bring this up to point out how fluid the terms used on this list
> can be. I guess I'm the network administrator of my house, and it appears
> that I've purchased a router that uses Google's DNS servers by default
> (fine with me). I hope my router is using DoH or DoT. If it's not, it might
> get updated to do so at some point--its software self updates all the time.
>
> thanks,
> Rob
>
> [1] https://www.whois.com/whois/172.253.0.2
> [2] https://tools.ietf.org/html/draft-livingood-dns-redirect-03
>