[DNSOP] Brief update on DNS Camel & Hello-DNS

bert hubert <bert.hubert@powerdns.com> Thu, 25 October 2018 15:36 UTC

Return-Path: <bert@hubertnet.nl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5A179130E7E for <dnsop@ietfa.amsl.com>; Thu, 25 Oct 2018 08:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Zwbm72SVfeXZ for <dnsop@ietfa.amsl.com>; Thu, 25 Oct 2018 08:36:47 -0700 (PDT)
Received: from xs.powerdns.com (xs.powerdns.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3E2E130E76 for <dnsop@ietf.org>; Thu, 25 Oct 2018 08:36:47 -0700 (PDT)
Received: from server.ds9a.nl (unknown []) by xs.powerdns.com (Postfix) with ESMTPS id C68429FB55 for <dnsop@ietf.org>; Thu, 25 Oct 2018 15:36:31 +0000 (UTC)
Received: by server.ds9a.nl (Postfix, from userid 1000) id 8474EAC9D41; Thu, 25 Oct 2018 17:36:31 +0200 (CEST)
Date: Thu, 25 Oct 2018 17:36:31 +0200
From: bert hubert <bert.hubert@powerdns.com>
To: dnsop@ietf.org
Message-ID: <20181025153631.GA32596@server.ds9a.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/nqamufjnfuUqqzEDUPf8_VCq9Ak>
Subject: [DNSOP] Brief update on DNS Camel & Hello-DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2018 15:36:49 -0000

Hi everyone,

After the most excellent DNS-OARC in Amsterdam, I got some new zeal to work
on DNS projects. In this message I request feedback & hope that some of you
may want to help.

DNS Camel Viewer
First, the "DNS Camel viewer" on https://powerdns.org/dns-camel/ has been
updated with the latest RFCs. I also used the IETF-provided XML of all RFCs
to find some missing RFCs by tracking 'updated-by'. Then I spent some loving
hours moving RFCs from categories like 'core' to 'dns-use'. The result of
this work is that if you only read 'core' and standards (track) DNS
documents, you now only have to work through 79 documents totalling 1257

In graph form, it now looks like this: https://twitter.com/PowerDNS_Bert/status/1054117820542398465

My request is: could you click through https://powerdns.org/dns-camel/ and
check if your favorite RFCs are there, and if they are in the right
categories? Changes can be entered through GitHub.

Hello DNS

Hello DNS is my effort to document DNS for newcomers, by 'flattening' the 79
RFCs you need to read into one narrative.  Slides and OARC presentation
video can be found through:

"Hello DNS" comes with documentation but also running code. There is an API for
parsing & creating DNS messages with most RRTYPEs supported. Based on that
library, there are implementations of 'tdig', 'tauth' and 'tres', which do
what you'd expect them to do. Finally, there is a very simple library you
can use to lookup IP addresses, MX and TXT records from C.

'tres' may be of specific interest, it was written after some prodding by
Evan Hunt. It is a 'workaround and cache free DNS resolver'. It is meant to
show how hard and painful it is to write a resolver. Oddly enough, this 400
line resolver appears to be workable. I've been using it to browse the web
for two weeks now and almost nothing is broken.

'tres' also creates fun 'graphviz' output on how it resolves domains.

My request is, could you click through 'hello-dns' and if you find anything
missing (it is still quite a lot), can you head to GitHub and submit more

Specifically in need of help:

https://powerdns.org/hello-dns/optional.md.html (on EDNS, Dynamic Updates,