Unable to listen on port 53 and run Blocky locally #1615
Answered
by
ChitranshuV
ChitranshuV
asked this question in
Q&A
-
|
The docs say
I have tried both of these methods and they didn't work out for me. I want to run blocky locally on my linux machine. I have configured my router to use Quad9's 9.9.9.9 and 149.112.112.112 for DNS. Blocky logs |
Beta Was this translation helpful? Give feedback.
Answered by
ChitranshuV
Sep 30, 2024
Replies: 2 comments
-
|
Hi, (Please post logs here inilne or as an attachment, paste services might go down or delete the data. I edited your post to include the logs)
Means something else is already using port 53. The good news is setting the capability worked, you'd get an "operation not permitted" error otherwise (not 100% on the exact error, that's from memory).
Actually I missed it was 127.0.0.53. I think it might be from a previous blocky run since ports aren't necessarily free to be reused immediately. Does this still happen if you try again now? |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi, I have solved this issue. Please see the steps below Disable and stop Systemd-Resolved for DNS resolution Make Network Manager handle DNS
Create a symlink to resolv.conf Restart Blocky Ensuring Blocky is used as DNS nameserver by all applications. This configuration tells NetworkManager to use 127.0.0.1 (where Blocky is listening) as the DNS server for all network connections (WiFi, Ethernet, etc.) without needing to configure each one individually. It should list 127.0.0.1 as the nameserver. Also adding more steps to start Blocky as user systemd service on boot. Change User and ExecStart according to your system.
I hope the @0xERR0R can add this in the documentation or some kind of FAQ section for future users. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
ChitranshuV
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I have solved this issue. Please see the steps below
Disable and stop Systemd-Resolved for DNS resolution
$ sudo systemctl disable systemd-resolved$ sudo systemctl stop systemd-resolvedMake Network Manager handle DNS
$ sudo nano /etc/NetworkManager/NetworkManager.confAdd the following under the [main] section:
$ sudo systemctl restart NetworkManagerCreate a symlink to resolv.conf
$ sudo rm /etc/resolv.conf$ sudo ln -s /run/NetworkManager/resolv.conf /etc/resolv.confRestart Blocky
$ ./blocky --config config.ymlEnsuring Blocky is used as DNS nameserver by all applications.
$ sudo nano /etc/NetworkManager/conf.d/dns-settings.conf