-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
--server doesnt work when pihole is running locally #448
Comments
Please run
And post the last lines of output |
I think I know what the issue is:
The dig command got answered with pi.hole, since but this machine is using itself and 1.1.1.1 as dns, pi.hole will resolve to be itself. More of the output if needed:
|
So you're having two Pi-holes in your network with both using the domain |
I changed webserver.domain to eap.lan, this fails because eap.lan has no dns entry on localhost Potential fix? Trying to resolve the domain via the server set with —server instead of implying that the host machine uses the pihole its PADDing to as DNS?
|
I think you are correct with your analysis. Let me think about how to properly fix this. (I think we had some internal discussion about |
We are likely not going to change the response for |
I submitted #450 , which removes the dns lookup for |
Thank you. I'll review after my vacation in around 2 weeks |
Describe the bug
running
./padd.sh --server 192.168.178.88 --secret shh
displays information on the pihole running locallyTo Reproduce
Steps to reproduce the behavior:
I have pihole running locally and my user is part of the
pihole
group.When running
./padd.sh --server 192.168.178.88 --secret shh
i get information displayed about the local pihole not the one on .88The ip needs to be running pihole, for example
./padd.sh --server 192.168.178.89 --secret shh
will result padd on getting stuck on the loading screen.Expected behavior
Display information about 192.168.178.88
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: