Replies: 1 comment
-
Hi @elXames, I don't run Mint, but I'll try and help ( in lieu of someone stepping in who knows better). I might be tempted to set 127.0.0.53 in the dnscrypt-proxy.toml file The way to stop nm overwrting resolv.conf is to edit QQ:
Were there any error messages? Was that part clean? I have a mini ubuntu server - that has resolv.conf set to 127.0.0.53 rather than the expected 127.0.0.1
|
Beta Was this translation helpful? Give feedback.
-
Hi there!
I tried setting up dnscrypt-proxy on a freshly installed Linux Mint system. I did everything as described in the 'Installation on Linux' section in the Wiki. But after stopping and disabling the systemd-resolved service and configuring the relsolv.conf file,
./dnscrypt-proxy -resolve ...
only spit out this:Unable to resolve: [read udp 127.0.0.1:44342->127.0.0.1:53: read: connection refused]
.Also, the resolv.conf file was reset with the following code:
# Generated by NetworkManager nameserver 127.0.0.53
.I have no clue how to fix this...
Beta Was this translation helpful? Give feedback.
All reactions