Date: Tue, 24 Feb 2026 12:42:53 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 293425] handbook: Sec 32.7 should describe how to configure client-side DNS-over-HTTPS (DoH) Message-ID: <bug-293425-9@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293425 Bug ID: 293425 Summary: handbook: Sec 32.7 should describe how to configure client-side DNS-over-HTTPS (DoH) Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Books & Articles Assignee: doc@FreeBSD.org Reporter: bms@FreeBSD.org Created attachment 268326 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=268326&action=edit Personal HOWTO for FreeBSD DoH client bringup Sec. 32.7. Domain Name System (DNS) of the FreeBSD Handbook does not explain to end-users how to configure DoH: https://docs.freebsd.org/en/books/handbook/network-servers/#network-dns This documentation currently only explains how to do the one-time setup of the local_unbound vendored service, and doesn't contain any examples or references on how to implement DoH out-of-the-box. I've attached a copy of my personal notes on how to actually do this, but they will need updating to reflect how resolvconf(8) actually behaves: 2026-02-05: Recursive DNS on pin unexpectedly broke. mDNS .local is fine. Previously, we had to disable IPv6 in /etc/rc.conf, because our Hyper-V host was bridging us to a WiFi adapter. Recursive DNS was lost when IPv6 was reenabled. Solution: do-ipv6: yes in /etc/unbound/unbound.conf. Also, /etc/unbound/forward.conf somehow got an IPv6 address since then, and did not supply an IPv4 fallback. There was a "generated by resolvconf" comment at the top of the file; I guess it came from DHCPv6 options. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-293425-9>