RFC 9462 "Discovery of Designated Resolvers" added the possibility to discover an encrypted DNS server (DoH/DoT) via an SVCB record. This is great when announcing the DNS server via DHCP / Router Advertisements, allowing machines in the network to easily discover and upgrade to DoH/DoT without requiring the user to fiddle with configurations.
I tried adding an SVCB record for _dns.resolver.arpa. manually but it turned out to be currently unsupported. https://github.com/miekg/dns already has support for SVCB records, so I assume this could be added easily?
But it would be better if blocky would support it out of the box, so that it can respond with the correct IP address for the interface the request came in from (if reachable on multiple networks).
RFC 9462 "Discovery of Designated Resolvers" added the possibility to discover an encrypted DNS server (DoH/DoT) via an SVCB record. This is great when announcing the DNS server via DHCP / Router Advertisements, allowing machines in the network to easily discover and upgrade to DoH/DoT without requiring the user to fiddle with configurations.
I tried adding an SVCB record for
_dns.resolver.arpa.
manually but it turned out to be currently unsupported. https://github.com/miekg/dns already has support for SVCB records, so I assume this could be added easily?But it would be better if blocky would support it out of the box, so that it can respond with the correct IP address for the interface the request came in from (if reachable on multiple networks).