Re: [DNSOP] Concerns around deployment of DNS over HTTPS (DoH)

Erik Kline <> Wed, 13 March 2019 19:24 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 76261130EF7 for <>; Wed, 13 Mar 2019 12:24:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -9.499
X-Spam-Status: No, score=-9.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id S2DBT2iV_gGo for <>; Wed, 13 Mar 2019 12:24:08 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::12b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7D8B9128AFB for <>; Wed, 13 Mar 2019 12:24:08 -0700 (PDT)
Received: by with SMTP id 188so736141itb.0 for <>; Wed, 13 Mar 2019 12:24:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=LE2vCB/hdc6KJiTMwKk8JOfgA06Goq0oOVvNJv3CXD0=; b=atrh2wWKS9SOtPBOio3BiSqfttwseSBo8fd3sloQIzz5l+cAjM3dZVQOXzErINxCHK sYQWfwTWPFqbWZuukvEsvjzOiI5pfCxLgPXRJB32G6B9WZRKUbNPDRxNydAb31x5hEUR /ZiOzT8cLmHlvc2q57NfmY9mD7MKDlBzhvYsw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=LE2vCB/hdc6KJiTMwKk8JOfgA06Goq0oOVvNJv3CXD0=; b=YTs0atyXacnXHAyPhU/5NEP6pdyRsU1cbassJslJg9faia6Jep8kISRGLKaCSs9Gik Tbde4wU+v2iFTkUdMmksgNceLSCOoDb7pmjGJ1w/7rkrJaTPI29qmYIOEH7K4tuGEvHN JzZ4wD1Z8VnpTOqCKXqi/V/WcCdqW5u2Sv7do3x9oqvbwqJJfw+ySE5Rw9qj0pzKqhA/ NIaBTCT1qWwjddnWp6bxh1d9INcR6XserAH4ixIetkD+BI9E3s8h9Dfko2XRzjEFYJVa bInkNSVtpfj4tanh7JqlnHB9rWPY+ormVrTN4pthF6MDqiRVFZuqnm/gP/qmlSVdV30E 6DAg==
X-Gm-Message-State: APjAAAWfis/aluxz51oO2uGag0iP7RSuJO7WtGz4F8T3K8GNKaNeVMsR QGHliqhiT5GTLs/pvDKBlZMKgvZAh7LhDVPX7d/kYr9mV0Q=
X-Google-Smtp-Source: APXvYqwq+zPhYib37c6+1e8A/NIrGHuGQ55yRtls+Py0aQTA4Epyj6GrTMZ0yYBuZGAMS1BMmq2li7N2cBusMC40O2k=
X-Received: by 2002:a24:2149:: with SMTP id e70mr2659261ita.23.1552505047526; Wed, 13 Mar 2019 12:24:07 -0700 (PDT)
MIME-Version: 1.0
References: <> <8490858.J4o6DMrmW6@linux-9daj> <>
In-Reply-To: <>
From: Erik Kline <>
Date: Wed, 13 Mar 2019 12:23:55 -0700
Message-ID: <>
To: Kenji Baheux <>
Cc: Paul Vixie <>, IETF DNSOP WG <>
Content-Type: multipart/alternative; boundary="000000000000df21b40583febf46"
Archived-At: <>
Subject: Re: [DNSOP] Concerns around deployment of DNS over HTTPS (DoH)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 13 Mar 2019 19:24:11 -0000

> If there is a malicious user or app on a network that someone is trying to
> protect, isn't the very existence of these players the actual issue that
> needs to be addressed?

I tend to think this is the real issue.  Any app can craft its own
non-cleartext-DNS name resolution service; DoH makes it a bit easier
perhaps, but not much (vis. JSON DNS, etc...).

My suspicion is that controlling a network's DNS is less and less likely to
be a decent control point for network security w.r.t. to the craftier
apps.  I'm sure the monitoring and interference with things looking up
"really-evil.evil" still has some value.  But much more sophistication is
probably required nowadays to deal with even moderately competent
adversaries...I suspect.