Closed anginear closed 1 year ago
This issue is stale because it has been open 30 days with no activity. Please comment or update this issue or it will be closed in 5 days.
Hey, I've resolved this issue by stopping systemd-resolved on my host system which was hogging up port 53.
I have a similar problem. When i add port=5353
to ./etc-dnsmasq.d/02-custom.conf
, it wont't start anymore (the same error). But i need to change the FTL DNSmasq port, because i want to use --net=host
AND using the original dnsmasq of the Linux operating system (because i need the feature nftset
).
I'm unable to change the FTL Port to a custom port (i do not mean docker port mapping - this will not work when using --net=host
).
Edit: I got it working. Accidentally, I wrote port 5353
instead of port=5353
🤦
I have a pihole installation on docker in macvlan mode running on Ubuntu 20.04. It was running fine but this morning, I am getting the following error. I've not made any changes to the server.