Re: net/dnscrypt-proxy README: dhclient -> resolvd/dhcpleased.conf

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.

-- 

  Sent from a phone, apologies for poor formatting.

On 6 July 2024 09:45:03 Klemens Nanni <kn@openbsd.org> wrote:

Not using this port, just grepped ports for dhclient and saw this.

Feedback? OK?

Index: net/dnscrypt-proxy//Makefile

===================================================================

RCS file: /cvs/ports/net/dnscrypt-proxy/Makefile,v

diff -u -p -r1.67 Makefile

--- net/dnscrypt-proxy//Makefile 8 Feb 2024 00:57:55 -0000 1.67

+++ net/dnscrypt-proxy//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: net/dnscrypt-proxy//pkg/README

===================================================================

RCS file: /cvs/ports/net/dnscrypt-proxy/pkg/README,v

diff -u -p -r1.5 README

--- net/dnscrypt-proxy//pkg/README 11 Mar 2022 19:45:54 -0000 1.5

+++ net/dnscrypt-proxy//pkg/README 6 Jul 2024 08:34:06 -0000

@@ -60,8 +60,8 @@ Set ${SYSCONFDIR}/resolv.conf to perform

 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.

+Note: If your IP address is dynamically fetched, resolvd(8) will normally

+update resolv.conf(5) with network-provided DNS servers. This can be avoided by

+using "ignore dns" in dhcpleased.conf(5).

 

 For more information, see https://dnscrypt.info/