ok.

On 2024/07/09 18:42, Klemens Nanni wrote:
> 06.07.2024 12:49, Stuart Henderson пишет:
> > That's better than the present doc, but the resolver can be picked up by slaacd and umb (and maybe also pppoe) and fed to resolve to rewrite the file - so in some cases it might be necessary to disable resolvd instead.
> 
> Right... we might as well leave explaining to manuals and provide a minimal
> working example;  everything dynamic ought to be clear enough for users to
> configure after learning how resolv.conf(5)/resolvd(5) actually works for us.
> 
> Feedback? OK?
> 
> Index: Makefile
> ===================================================================
> RCS file: /cvs/ports/net/dnscrypt-proxy/Makefile,v
> diff -u -p -r1.67 Makefile
> --- Makefile	8 Feb 2024 00:57:55 -0000	1.67
> +++ Makefile	6 Jul 2024 08:34:23 -0000
> @@ -3,7 +3,7 @@ COMMENT =	flexible DNS proxy with suppor
>  GH_ACCOUNT =	jedisct1
>  GH_PROJECT =	dnscrypt-proxy
>  GH_TAGNAME =	2.1.5
> -REVISION =	1
> +REVISION =	2
>  
>  CATEGORIES =	net
>  
> Index: pkg/README
> ===================================================================
> RCS file: /cvs/ports/net/dnscrypt-proxy/pkg/README,v
> diff -u -p -r1.5 README
> --- pkg/README	11 Mar 2022 19:45:54 -0000	1.5
> +++ pkg/README	9 Jul 2024 18:38:53 -0000
> @@ -55,13 +55,10 @@ Start the daemon:
>  resolv.conf
>  ===========
>  
> -Set ${SYSCONFDIR}/resolv.conf to perform queries from dnscrypt-proxy:
> +Managed by resolvd(8). One way is to disable it and force
> +${SYSCONFDIR}/resolv.conf to perform queries from dnscrypt-proxy:
>  
>  nameserver 127.0.0.1
>  lookup file bind
> -
> -Note: If your IP address is dynamically fetched, dhclient(8) will normally
> -update resolv.conf with network-provided DNS servers. This can be avoided by
> -using "ignore domain-name, domain-name-servers;" in ${SYSCONFDIR}/dhclient.conf.
>  
>  For more information, see https://dnscrypt.info/
>