This gave birth to a new tool we call dsc-datatool and this tool can read the DSC XML data and convert it into InfluxDB, which is one of the backends Grafana supports. The tool itself can have support for many different input and output formats and also has other modules called Generators and Transformers.
These Generators and Transformers can be used to generate additional data and transform it in various ways, for example there is a transformer called Labler which can rewrite QTYPE/RCODE's to their textual name and a generator called client_subnet_country which will generate additional datasets based on client_subnet that will summarize the statistics based on the subnets country instead of the subnet itself.
If you’re attending OARC 25 in Dallas you will have the chance to test a local installation of DSC Grafana which will be set up for an interactive demonstration for the whole of the conference and I will be around to answer any questions you might have regarding it.
Check My DNS
The Check My DNS project is a continuation of all the DNS testers that we already have. Since the testers share design, implementation and/or code this project aims to combine them all and support new tests with a specific framework for testing the resolver side of DNS.
As a start we now have tests for QNAME Minimization, DNSSEC, TCP and IPv6 Connectivity with future plans to add tests for DANE/TLSA, Reply Size, Port and DNS Entropy. Beside these tests we also detect if the resolvers are using TLS, TCP or UDP and IPv4 or IPv6.
The DNS server has the capability to generate unique/never-seen-before zones that can be delegated and spread out over an IP range. These zones are then queried by the browser in order to use the clients resolvers and all queries and results are stored for retrieval from the REST API.
If you have any ideas about something we should test or would like to know more please contact us.
The DNS-OARC team have reviewed the licenses used in our projects and is proposing to change them and categorize projects into the following categories. These categories will also be of help when starting new projects, picking where they belongs and the license.
Projects that are publicly available for example the software DSC and DNSCAP on GitHub.
As most of our software today is in 2 or 3-clause BSD we want to move to a stronger license in the open source sense, ensure cooperation with the community and to prepare for it to be included in major distributions.
Projects for which the source-code is members-only, or services that we run both publicly and members only. For example, some of these projects would be the testers we have (DNS Entropy, Reply Size) and the tools used for DITL.
For these projects we want to use the MPL-2.0 license which we feel is a stronger alternative to 2/3-clause BSD. This license would also make it easier for us to cooperate mid-project and/or create larger work without changing it.
Note that these categories and licenses are not final, if we have a project that would be better with a different license we will choose that license.