On 2022-03-26, Florian Obser <flor...@openbsd.org> wrote: > On 2022-03-25 20:07 UTC, Stuart Henderson <stu.li...@spacehopper.org> wrote: >> (I found unwind more trouble than it's worth with rdomains though, >> I killed resolvd and hardcoded a public resolver in resolv.conf >> instead..) > > Do we need something simpler for some rdomain setups? A daemon listening > on 127.0.0.1 and only forwarding to a fixed server? I.e. bring back > rebound for this?
I think the main issue is that you often want a different config per rdomain and it gets hard to manage (and resolv.conf applies to software running in all domains). Though actually multiple unwinds and explicitly configuring 127.0.0.1 on loX for the various rdomains might be a way around that.. If you don't want to separate them, for forwarding it seems that e.g. "match on lo2 to self rtable 0" does the trick.
