-
-
Notifications
You must be signed in to change notification settings - Fork 562
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Admin interface reports "DNS Service not running" when pihole-FTL runs on a non-standard port. #2030
Comments
Thanks for the report. Fixing the "issue" is not a problem, however, I would like to discuss if we really should fix this. DNS runs by default on port 53. If users are so advanced to change the port to something different, they need an advanced network knowledge and configuration. One way out would be to simply change the message to "DNS service not running on port 53" - but I'm not sure if this is what you aimed for. |
I didn't have a direct aim. I understand the "fix" is easy, and I half expected a response along the lines of that you gave me. Which I'm completely okay with. I totallyssee where you're coming from. |
@bdoner Please try if
You can got back to the master branch by |
Hi @yubiuser, It looks really good on my end. I have left a single comment to your PR. But apart from that nothing to note :) |
Fix has been released to master with |
Versions
Platform
Expected behavior
I expect the admin interface to report the DNS Service (pihole-FTL) to be running, when it is in fact running and functioning.
Actual behavior / bug
The admin interface reports "DNS service not running" under Status in the side-menu.
Steps to reproduce
Steps to reproduce the behavior:
Change pihole-FTL to run on a non-standard port (something not port 53).
/etc/dnsmasq.d/01-pihole.conf
port=12345
in the config.# systemctl restart pihole-FTL
)Debug Token
N/A
Screenshots
Additional context
Issue occurs on line 319 of the pihole script where it's checked if the service is listening on port 53 instead of checking if the service is running.
The text was updated successfully, but these errors were encountered: