From 525f8e66c55e1653f9646fab9f810d870cc70afa Mon Sep 17 00:00:00 2001 From: DoTheEvolution Date: Tue, 19 May 2020 22:34:36 +0200 Subject: [PATCH] update --- dnsmasq/readme.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/dnsmasq/readme.md b/dnsmasq/readme.md index 6676a78..a4dbc5e 100644 --- a/dnsmasq/readme.md +++ b/dnsmasq/readme.md @@ -172,10 +172,11 @@ rule. So `example.com` stuff here is just for show. `sudo systemctl enable --now dnsmasq` * Check if it started without errors: `journalctl -u dnsmasq.service` -* If you get port already in use error, check which service
+* If you get "port already in use" error, check which service is responsible
`sudo ss -tulwnp`
If you are using `systemd-networkd` along with `systemd-resolved`, - it will likely be `systemd-resolved`.
+ it will likely be `systemd-resolved` so stop it and disable it.
+ `sudo systemctl disable --now systemd-resolved` * Make sure you **disable other DHCP servers** on the network, usually a router is running one.