[Doh] DoT and DoH at Cambridge

Tony Finch <dot@dotat.at> Thu, 06 September 2018 09:35 UTC

Return-Path: <dot@dotat.at>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CA1B130DC8 for <doh@ietfa.amsl.com>; Thu, 6 Sep 2018 02:35:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 V5ZgP9mT6AdZ for <doh@ietfa.amsl.com>; Thu, 6 Sep 2018 02:35:38 -0700 (PDT)
Received: from ppsw-31.csi.cam.ac.uk (ppsw-31.csi.cam.ac.uk [131.111.8.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3975E128B14 for <doh@ietf.org>; Thu, 6 Sep 2018 02:35:38 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:36634) by ppsw-31.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.137]:25) with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) id 1fxqhL-000qGn-ME (Exim 4.91) (return-path <dot@dotat.at>); Thu, 06 Sep 2018 10:35:35 +0100
Date: Thu, 06 Sep 2018 10:35:35 +0100
From: Tony Finch <dot@dotat.at>
To: doh@ietf.org, dprive@ietf.org
Message-ID: <alpine.DEB.2.20.1809061011520.5965@grey.csi.cam.ac.uk>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/I-ytiO6ykbt9krrC9FVGEFo-CA4>
Subject: [Doh] DoT and DoH at Cambridge
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Sep 2018 09:35:40 -0000

Yesterday I deployed doh101 (https://github.com/fanf2/doh101/) on
Cambridge University's central recursive DNS servers. These are currently
doing about 2000 Do53 qps total (out of term - they will be busier in
October).

A few operational notes that may be of interest:

## DNS-over-TLS

I expected this to have a small amount of traffic initially, ramping up as
Android 9 "pie" devices (which do opportunistic DoT) become more common.
But I was immediately getting a few DoT qps.

On further investigation the vast majority of these were queries like
RRRRRR-dnsotls-ds.metric.gstatic.com (where RRRRRR is random) from devices
on eduroam. So to me it looks like Google are measuring availability of
DoT support using some small proportion of Android users. (1% of recent
versions?)

Real DoT queries for useful qnames were negligible (but not zero) as
expected.

## DNS-over-HTTPS

I'm using Firefox 62 (I upgraded from 61 while I was fiddling around with
it yesterday afternoon) and I have adjusted its network.trr settings to
use my DoH servers.

I accept application/dns-udpwireformat to support Firefox's older DoH
implementation, as well as application/dns-message.

With trr.mode = 3 (strictly DoH only) it seems a bit brittle: sometimes
Firefox will decide to stop talking to the DoH servers for some unknown
reason. trr.mode = 2 (DoH first with fallback to system resolver) works
more reliably.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Malin: Northwest 5 or 6. Moderate. Showers. Good.