systemd sockets don't work, so don't recommend that for now

Installation-Debian-Ubuntu.md

@@ -41,7 +41,7 @@ managed=false
 
 #### Proceeding with dnsmasq
 If you want to continue to use dnsmasq (default on Ubuntu), some configuration is needed:
-- dnsmasq listens on `127.0.0.1:53`, so configure dnscrypt-proxy to use something different (e.g. `127.0.2.1:53`, see `dnscrypt-proxy.socket` or `listen_addresses` in `dnscrypt-proxy.toml`)
+- dnsmasq listens on `127.0.0.1:53`, so configure dnscrypt-proxy to use something different (e.g. `127.0.2.1:53`, see `listen_addresses` in `dnscrypt-proxy.toml`)
 - configure dnsmasq to use dnscrypt-proxy if file not already configured:
 
  ```sh
@@ -151,4 +151,4 @@ $ sudo ./dnscrypt-proxy -service start
 $ dnscrypt-proxy -resolve github.com
 $ ping -c1 dnscrypt.info # Should show Server matching nameserver, e.g. 127.0.0.1, in resolv.conf
 $ sudo tcpdump  # Should show specific resolver if it is not rotating
-```
+```

Installation-linux.md

@@ -244,6 +244,6 @@ In order to install a new version, just replace the executable file (`dnscrypt-p
 
 ## Usage with systemd
 
-`dnscrypt-proxy` can be started with systemd. It can also handle sockets created by systemd ("socket activation").
+`dnscrypt-proxy` can be started with systemd.
 
 Since this is a complicated topic for experienced Linux users, there is a dedicated page: [dnscrypt-proxy with systemd](systemd).

systemd.md

@@ -1,6 +1,8 @@
 # Usage with systemd
 
-`dnscrypt-proxy` can be started with systemd, and can also handle sockets created by systemd ("socket activation").
+`dnscrypt-proxy` can be started with systemd.
+
+Socket emulation from systemd ("socket activation") may work but this is not a well-tested configuration. Use native sockets (`listen_addresses` in the `dnscrypt-proxy.toml` configuration file) whenever possible.
 
 Packages from distribution repositories (e.g. Arch Linux) may set up systemd sockets by default.