The DNS records with RR type SSHFP (SSH Finger Print value 44) are displayed as TYPE44.
It would be nicer to display SSHFP instead.
This record type has been defined in RFC 4255 from 2006.
The SSHFP Resource Record
The SSHFP resource record (RR) is used to store a fingerprint of an
SSH public host key that is associated with a Domain Name System
(DNS) name.The RR type code for the SSHFP RR is 44.
Thanks for your suggestion. I wonder, if, at some point (it may be now), we should just implement the entirety of Domain Name System (DNS) Parameters. The downside to this is that it'd may make the Javascript on the web interface quite large. This would have to be evaluated.
Any more thoughts on this?
No objection from me 
For now the only RR type I have in the OTHER category is the SSHFP/type 44.
But I have a very small network with few DNS clients.
For the benefit of casual readers, I'd first like to clarify that -contrary to what the current topic title may suggest- pihole-FTL/dnsmasq is quite capable of handling SSHFP RR types already - it's just Pi-hole's UI that doesn't decode 44 into a directly readable representation.
From a maintenance perspective, incorporating full translation support would mean to introduce a third-party release dependency, i..e any time a new RR type would be added or amended, this would require a new release of Pi-hole.
To mitigate or avoid this, we'd either have to keep the generic OTHER type for currently unknown types, or maybe host a translation file publically where updated translations can be published without the requirement of rolling out a new Pi-hole release.
Yes, that's what I wanted to do. Also to summarize the custom/reserved RR types. I do not want to run after newly added RR types, this missing SSHFP UI interpretation is the only the second request I've ever seen in Pi-hole's lifetime (the first war was HTTPS)
I felt like this should be added server-side. Hence, I sent a patch upstream to dnsmasq that implements all RR types are defined by IANA in the table given in the link above. We'll see what the response will be.
From 97ca3ae9ff6a33ac70fb982d282a1728dee5a9cd Mon Sep 17 00:00:00 2001
From: Dominik DL6ER <dl6er@dl6er.de>
Date: Thu, 9 Sep 2021 14:28:28 +0200
Subject: [PATCH] Implement all known RRtypes defined by IANA
Signed-off-by: DL6ER <dl6er@dl6er.de>
---
src/cache.c | 130 ++++++++++++++++++++++++++++++++++++----------------
1 file changed, 90 insertions(+), 40 deletions(-)
diff --git a/src/cache.c b/src/cache.c
index 8add610..843907d 100644
--- a/src/cache.c
+++ b/src/cache.c
@@ -30,50 +30,100 @@ static struct crec *really_insert(char *name, union all_addr *addr, unsigned sho
time_t now, unsigned long ttl, unsigned int flags);
/* type->string mapping: this is also used by the name-hash function as a mixing table. */
+/* taken from https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml */
static const struct {
unsigned int type;
const char * const name;
} typestr[] = {
- { 1, "A" },
+ { 1, "A" }, /* a host address [RFC1035] */
- { 2, "NS" },
+ { 2, "NS" }, /* an authoritative name server [RFC1035] */
+ { 3, "MD" }, /* a mail destination (OBSOLETE - use MX) [RFC1035] */
+ { 4, "MF" }, /* a mail forwarder (OBSOLETE - use MX) [RFC1035] */
- { 5, "CNAME" },
+ { 5, "CNAME" }, /* the canonical name for an alias [RFC1035] */
- { 6, "SOA" },
+ { 6, "SOA" }, /* marks the start of a zone of authority [RFC1035] */
+ { 7, "MB" }, /* a mailbox domain name (EXPERIMENTAL) [RFC1035] */
+ { 8, "MG" }, /* a mail group member (EXPERIMENTAL) [RFC1035] */
+ { 9, "MR" }, /* a mail rename domain name (EXPERIMENTAL) [RFC1035] */
- { 10, "NULL" },
+ { 10, "NULL" }, /* a null RR (EXPERIMENTAL) [RFC1035] */
- { 11, "WKS" },
+ { 11, "WKS" }, /* a well known service description [RFC1035] */
- { 12, "PTR" },
+ { 12, "PTR" }, /* a domain name pointer [RFC1035] */
- { 13, "HINFO" },
+ { 13, "HINFO" }, /* host information [RFC1035] */
+ { 14, "MINFO" }, /* mailbox or mail list information [RFC1035] */
- { 15, "MX" },
+ { 15, "MX" }, /* mail exchange [RFC1035] */
- { 16, "TXT" },
+ { 16, "TXT" }, /* text strings [RFC1035] */
+ { 17, "RP" }, /* for Responsible Person [RFC1183] */
+ { 18, "AFSDB" }, /* for AFS Data Base location [RFC1183][RFC5864] */
+ { 19, "X25" }, /* for X.25 PSDN address [RFC1183] */
+ { 20, "ISDN" }, /* for ISDN address [RFC1183] */
+ { 21, "RT" }, /* for Route Through [RFC1183] */
- { 22, "NSAP" },
+ { 22, "NSAP" }, /* for NSAP address, NSAP style A record [RFC1706] */
- { 23, "NSAP_PTR" },
+ { 23, "NSAP_PTR" }, /* for domain name pointer, NSAP style [RFC1348][RFC1637][RFC1706] */
- { 24, "SIG" },
+ { 24, "SIG" }, /* for security signature [RFC2535][RFC2536][RFC2537][RFC2931][RFC3008][RFC3110][RFC3755][RFC4034] */
- { 25, "KEY" },
+ { 25, "KEY" }, /* for security key [RFC2535][RFC2536][RFC2537][RFC2539][RFC3008][RFC3110][RFC3755][RFC4034] */
+ { 26, "PX" }, /* X.400 mail mapping information [RFC2163] */
+ { 27, "GPOS" }, /* Geographical Position [RFC1712] */
- { 28, "AAAA" },
+ { 28, "AAAA" }, /* IP6 Address [RFC3596] */
- { 29, "LOC" },
+ { 29, "LOC" }, /* Location Information [RFC1876] */
+ { 30, "NXT" }, /* Next Domain (OBSOLETE) [RFC2535][RFC3755] */
+ { 31, "EID" }, /* Endpoint Identifier [Michael_Patton][http://ana-3.lcs.mit.edu/~jnc/nimrod/dns.txt] 1995-06*/
+ { 32, "NIMLOC" }, /* Nimrod Locator [1][Michael_Patton][http://ana-3.lcs.mit.edu/~jnc/nimrod/dns.txt] 1995-06*/
- { 33, "SRV" },
+ { 33, "SRV" }, /* Server Selection [1][RFC2782] */
+ { 34, "ATMA" }, /* ATM Address [ ATM Forum Technical Committee, "ATM Name System, V2.0", Doc ID: AF-DANS-0152.000, July 2000. Available from and held in escrow by IANA.] */
- { 35, "NAPTR" },
+ { 35, "NAPTR" }, /* Naming Authority Pointer [RFC2168][RFC2915][RFC3403] */
- { 36, "KX" },
+ { 36, "KX" }, /* Key Exchanger [RFC2230] */
- { 37, "CERT" },
+ { 37, "CERT" }, /* CERT [RFC4398] */
- { 38, "A6" },
+ { 38, "A6" }, /* A6 (OBSOLETE - use AAAA) [RFC2874][RFC3226][RFC6563] */
- { 39, "DNAME" },
+ { 39, "DNAME" }, /* DNAME [RFC6672] */
+ { 40, "SINK" }, /* SINK [Donald_E_Eastlake][http://tools.ietf.org/html/draft-eastlake-kitchen-sink] 1997-11*/
- { 41, "OPT" },
+ { 41, "OPT" }, /* OPT [RFC3225][RFC6891] */
+ { 42, "APL" }, /* APL [RFC3123] */
- { 43, "DS" },
- { 46, "RRSIG" },
+ { 43, "DS" }, /* Delegation Signer [RFC3658][RFC4034] */
+ { 44, "SSHFP" }, /* SSH Key Fingerprint [RFC4255] */
+ { 45, "IPSECKEY" }, /* IPSECKEY [RFC4025] */
+ { 46, "RRSIG" }, /* RRSIG [RFC3755][RFC4034] */
- { 47, "NSEC" },
+ { 47, "NSEC" }, /* NSEC [RFC3755][RFC4034][RFC9077] */
- { 48, "DNSKEY" },
+ { 48, "DNSKEY" }, /* DNSKEY [RFC3755][RFC4034] */
+ { 49, "DHCID" }, /* DHCID [RFC4701] */
- { 50, "NSEC3" },
- { 51, "NSEC3PARAM" },
+ { 50, "NSEC3" }, /* NSEC3 [RFC5155][RFC9077] */
+ { 51, "NSEC3PARAM" }, /* NSEC3PARAM [RFC5155] */
- { 52, "TLSA" },
+ { 52, "TLSA" }, /* TLSA [RFC6698] */
- { 53, "SMIMEA" },
+ { 53, "SMIMEA" }, /* S/MIME cert association [RFC8162] SMIMEA/smimea-completed-template 2015-12-01*/
- { 55, "HIP" },
+ { 55, "HIP" }, /* Host Identity Protocol [RFC8005] */
+ { 56, "NINFO" }, /* NINFO [Jim_Reid] NINFO/ninfo-completed-template 2008-01-21*/
+ { 57, "RKEY" }, /* RKEY [Jim_Reid] RKEY/rkey-completed-template 2008-01-21*/
+ { 58, "TALINK" }, /* Trust Anchor LINK [Wouter_Wijngaards] TALINK/talink-completed-template 2010-02-17*/
+ { 59, "CDS" }, /* Child DS [RFC7344] CDS/cds-completed-template 2011-06-06*/
+ { 60, "CDNSKEY" }, /* DNSKEY(s) the Child wants reflected in DS [RFC7344] 2014-06-16*/
+ { 61, "OPENPGPKEY" }, /* OpenPGP Key [RFC7929] OPENPGPKEY/openpgpkey-completed-template 2014-08-12*/
+ { 62, "CSYNC" }, /* Child-To-Parent Synchronization [RFC7477] 2015-01-27*/
+ { 63, "ZONEMD" }, /* Message Digest Over Zone Data [RFC8976] ZONEMD/zonemd-completed-template 2018-12-12*/
+ { 64, "SVCB" }, /* Service Binding [draft-ietf-dnsop-svcb-https-00] SVCB/svcb-completed-template 2020-06-30*/
+ { 65, "HTTPS" }, /* HTTPS Binding [draft-ietf-dnsop-svcb-https-00] HTTPS/https-completed-template 2020-06-30*/
+ { 99, "SPF" }, /* [RFC7208] */
+ { 100, "UINFO" }, /* [IANA-Reserved] */
+ { 101, "UID" }, /* [IANA-Reserved] */
+ { 102, "GID" }, /* [IANA-Reserved] */
+ { 103, "UNSPEC" }, /* [IANA-Reserved] */
+ { 104, "NID" }, /* [RFC6742] ILNP/nid-completed-template */
+ { 105, "L32" }, /* [RFC6742] ILNP/l32-completed-template */
+ { 106, "L64" }, /* [RFC6742] ILNP/l64-completed-template */
+ { 107, "LP" }, /* [RFC6742] ILNP/lp-completed-template */
+ { 108, "EUI48" }, /* an EUI-48 address [RFC7043] EUI48/eui48-completed-template 2013-03-27*/
+ { 109, "EUI64" }, /* an EUI-64 address [RFC7043] EUI64/eui64-completed-template 2013-03-27*/
- { 249, "TKEY" },
+ { 249, "TKEY" }, /* Transaction Key [RFC2930] */
- { 250, "TSIG" },
+ { 250, "TSIG" }, /* Transaction Signature [RFC8945] */
- { 251, "IXFR" },
+ { 251, "IXFR" }, /* incremental transfer [RFC1995] */
- { 252, "AXFR" },
+ { 252, "AXFR" }, /* transfer of an entire zone [RFC1035][RFC5936] */
- { 253, "MAILB" },
+ { 253, "MAILB" }, /* mailbox-related RRs (MB, MG or MR) [RFC1035] */
- { 254, "MAILA" },
+ { 254, "MAILA" }, /* mail agent RRs (OBSOLETE - see MX) [RFC1035] */
- { 255, "ANY" },
+ { 255, "ANY" }, /* A request for some or all records the server has available [RFC1035][RFC6895][RFC8482] */
+ { 256, "URI" }, /* URI [RFC7553] URI/uri-completed-template 2011-02-22*/
- { 257, "CAA" }
+ { 257, "CAA" }, /* Certification Authority Restriction [RFC8659] CAA/caa-completed-template 2011-04-07*/
+ { 258, "AVC" }, /* Application Visibility and Control [Wolfgang_Riedel] AVC/avc-completed-template 2016-02-26*/
+ { 259, "DOA" }, /* Digital Object Architecture [draft-durand-doa-over-dns] DOA/doa-completed-template 2017-08-30*/
+ { 260, "AMTRELAY" }, /* Automatic Multicast Tunneling Relay [RFC8777] AMTRELAY/amtrelay-completed-template 2019-02-06*/
+ { 32768, "TA" }, /* DNSSEC Trust Authorities [Sam_Weiler][http://cameo.library.cmu.edu/][ Deploying DNSSEC Without a Signed Root. Technical Report 1999-19, Information Networking Institute, Carnegie Mellon University, April 2004.] 2005-12-13*/
+ { 32769, "DLV" }, /* DNSSEC Lookaside Validation (OBSOLETE) [RFC8749][RFC4431] */
};
static void cache_free(struct crec *crecp);
--
2.25.1
This patch has been accepted upstream. The next version of Pi-hole will be able to display all known query types in the Query Log. We will still summarize those seldomly seen query types (such as SSHFP) as a common OTHER type on the dashboard just to keep the doughnut, or rather its legend, from exploding.
Just a screenshot how if currently looks like on the update/dnsmasq branch:
Note the square brackets around the type indicating that this is a query type that is subsumed under OTHER in the statistics.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.
