On 26 December 2020 17:59:45 CET, Klemens Nanni <[email protected]> wrote:
>I use unwind on my notebook where one particular domain must always go
>through one particular resolver; this resolver should should not be
>used for anything else.
>
>Hence I overwrite the default preference list (output of
>`unwind -vnf/dev/null') by removing `oDoT-forwarder' and `forwarder'
>such that unwind never tries it for any query by default.
>
>unwind.conf then looks like this:
>
> # special domain
> forwarder { 2001:db9::1 }
> force accept bogus forwarder { example.com. }
>
> # default with forwarder disabled
> preference { DoT recursor oDoT-dhcp dhcp stub }
>
>This does not work however because removing `forwarder' from the list
>also prevents the `force' block from working, i.e. despite an explicit
>"always use this type for this domain" unwind still honours the global
>default and therefore never tries the forwarder even for forced
>domains.
>
>
>Is this working as intended, e.g. am misinterpreting the wording in
>unwind.conf(5)?
I'd say it's a bug.
>
> preference {type ...}
> A list of DNS name server types to specify the order in which
> name servers are picked when measured round-trip time medians are
> equal. [...]
>
> force [accept bogus] type {name ...}
> Force resolving of name and its subdomains by the given resolver
> type. If accept bogus is specified validation is not enforced.
--
Sent from a mobile device. Please excuse poor formating.
