Skip to content

[DNSCrypt] systemd sockets disabled and dnscrypt-proxy-resolvconf file. #1394

@ghost

Description

Hello.

First, the most important thing: I want to thank Mr Frank Denis (and other Developers) for creating such an amazing and important application. Without your works, DNS privacy could depend only on two solutions explored by, amongst others, the IETF.

I have a question about the DNSCrypt with systemd sockets disabled and dnscrypt-proxy-resolvconf.service file. Is this file needed or can it be disabled along with dnscrypt-proxy.socket file? I'm asking because it seems, that this is file is not needed. DNSCrypt works okay and there are such an informations in Status:

[NOTICE] Now listening to 127.0.2.1:53 [UDP]
[NOTICE] Now listening to 127.0.2.1:53 [TCP]

Because dnscrypt-proxy-resolvconf.service file is used to gather a nameserver IP address (vide ExecStart{,Stop} options) from the dnscrypt-proxy.socket file and this address is already added, defined in dnscrypt-proxy.toml file (via listen_addresses option), it seems that dnscrypt-proxy-resolvconf.service file is not needed. Am I right?

Or maybe it's opposite and this file is needed because of lo.dnscrypt-proxy? (dnscrypt-proxy-resolvconf.service file, contains /sbin/resolvconf command, used twice with -a and -d options etc.) There are such possibilities:

  • leave dnscrypt-proxy.service and dnscrypt-proxy-resolvconf.service file.
  • leave dnscrypt-proxy.service only and disable dnscrypt-proxy-resolvconf.service file (what about lo.dnscrypt-proxy? Is it important, necessary?)

So, what should be done with dnscrypt-proxy-resolvconf.service file? In case when systemd sockets are disabled, of course.

Sorry, for such a long message.

Best regards.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions