On Fri, Nov 06, 2026 at 10:50:57AM -0500, [email protected] wrote:
> On 2026-11-06 7:58:50, Roderick wrote:
> > How I get that the system do not touch /etc/resolv.conf?
> >
> > In my notes, I wrote that "rcctl disable resolvd" is necessary, but in
> > my new installation of OpenBSD 8.0 does not work. I also remember that
> > something else was necessary.
>
> "resolvd" is still in 8.0 same as always and it starts by default.
>
> Besides the "rcctl disable resolvd" you will want to also do
> "rcctl stop resolvd" to stop the daemon already running.
> After the daemon is stopped (does not appear in "ps -auxw" output)
> verify that /etc/rc.conf.local has the line "resolvd_flags=NO"
> then edit /etc/resolv.conf to be like how you want it.
>
> > Another question: is unwind a replacement of unbound?
> > Does it write files or just keep a cache in memory? What is its
> > advantage over unbound?
>
> The first couple paragraphs of "man unwind" should answer that.
>
> Unbound is THE resolver whereas unwind forwards queries to the resolver.
Unwind can do resolving itself as well.
-Otto
> Most computers do not (should not) be running unbound directly.
> resolvd and unwind are ran on clients but neither is required to use DNS,
> they exist to help clients that move between networks to adapt to changing
> DNS IP addresses, unique to each network the client connects to.
>
> > Unfortunately, due to the cheap router falsifying DNS answers, I
> > cannot anymore use a recursive resolver.
>
> Most routers should have a setting to adjust that, if not:
> replace the router or replace its' firmware.
>
> > At best forwarding and requesting over TLS.
>
> Nothing wrong with DoT and DoH, many public resolvers support them.
> With unwind you can use DoT on public resolvers if you want to do that.
> If you are using unbound to do recursion yourself then UDP 53 must work.
>
