Stéphane Bortzmeyer

It would be nice to have DoH (RFC 8484) support in the server. See the work done at the IETF hackathon https://www.bortzmeyer.org/hackathon-ietf-101.html

Currently, we produce JSON according to a proprietary format. (See JSON.txt) It would be nice to have also the output format described in RFC 8427, tagged as application/dns+json

https://dns.bortzmeyer.org/hubone.me/CAA Unknown record type (257) Unknown record type (257) Unknown record type (257) Unknown record type (257) Better formatting wished

``` Query for domain _443._tcp.www.bortzmeyer.org., type TLSA Unknown record type (52) (Time-to-Live of this answer is 1 day, 0 second) ``` A better formatting is wished.

Example is syndirag.dirag.meteo.fr.

Several records in https://dns.bortzmeyer.org/dangerousrecord.broken-on-purpose.generic-nic.net/MX are not interpreted correctly when you click on it (lack of escape) : Record type SRC='HTTP: does not exist or things like that.

Python 2 is now clearly going to be deprecated so a port to Python 3 is necessary. (Before we resume fixing bugs.)

500 Internal Server Error on https://dns.bortzmeyer.org/e164enum.net/NS?server=e.gtld-servers.net (but it crashes for every domain and server)

Algorithm to handle DNSSEC validation errors when there are multiple resovers?

1

When the DNS looking glas uses several resolvers, and when they have a different use of DNSSEC (for instance, some validate and some don't), the results are not perfect. Unfortunately,...

To do so, a RESTful solution is to use the Prefer: HTTP header (RFC approved but not yet published): GET /example.org/AAAA HTTP/1.0 Prefer: wait=10