Review of 2018

2019-01-11 - Progress - Tony Finch

Some notes looking back on what happened last year...

Stats

1457 commits

4035 IP Register / MZS support messages

5734 cronspam messages

Projects

• New DNS web site (Feb, Mar, Jun, Sep, Oct, Nov)

  This was a rather long struggle with a lot of false starts, e.g. February / March finding that Perl Template Toolkit was not very satisfactory; realising after June that the server naming and vhost setup was unhelpful.

  End result is quite pleasing

• IP Register API extensions (Aug)

  API access to xlist_ops

  MWS3 API generalized for other UIS services

  Now in active use by MWS, Drupal Falcon, and to a lesser extent by the HPC OpenStack cluster and the new web Traffic Managers. When old Falcon is wound down we will be able to eliminate Gossamer!

• Server upgrade / rename (Dec)

  Lots of Ansible review / cleanup. Satisfying.

Future of IP Register

• Prototype setup for PostgreSQL replication using repmgr (Jan)

• Prototype infrastructure for JSON-RPC API in Typescript (April, May)

Maintenance

• DHCP servers upgraded to match rest of IP Register servers (Feb)

• DNS servers upgraded to BIND 9.12, with some serve-stale related problems. (March)

  Local patches all now incorporated upstream :-)

• git.uis continues, hopefully not for much longer

IETF

• Took over as the main author of draft-ietf-dnsop-aname. This work is ongoing.

• Received thanks in RFC 8198 (DNSSEC negative answer synthesis), RFC 8324 (DNS privacy), RFC 8482 (minimal ANY responses), RFC 8484 (DNS-over-HTTPS).

Open Source

• Ongoing maintenance of regpg. This has stabilized and reached a comfortable feature plateau.

• Created doh101, a DNS-over-TLS and DNS-over-HTTPS proxy.

  Initial prototype in March at the IETF hackathon.

  Revamped in August to match final IETF draft.

  Deployed in production in September.

• Fifteen patches committed to BIND9.

  CVE-2018-5737; extensive debugging work on the serve-stale feature.

  Thanked by ISC.org in their annual review.

• Significant clean-up and enhancement of my qp trie data structure, used by Knot DNS. This enabled much smaller memory usage during incremental zone updates.

  https://gitlab.labs.nic.cz/knot/knot-dns/issues/591

What's next?

• Update superglue delegation maintenance script to match the current state of the world. Hook it in to dnssec-keymgr and get automatic rollovers working.

• Rewrite draft-ietf-dnsop-aname again, in time for IETF104 in March.

• Server renumbering, and xfer/auth server split, and anycast. When?

• Port existing ipreg web interface off Jackdaw.

• Port database from Oracle on Jackdaw to PostgreSQL on my servers.

• Develop new API / UI.

• Re-do provisioning system for streaming replication from database to DNS.

• Move MZS into IP Register database.