Please follow the below template, it will help us to help you!
If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx instead of lighttpd, or there is some other aspect of your install that is customised) - please use the Community Help category.
Expected Behaviour:
Able to use Pihole IP as my DNS to use ads block feature.
I install Pi-Hole on a Intel Dual Core PC with Kubuntu as OS. The server has currently deployed with nextcloud and Pi-Hole and that
Actual Behaviour:
Couldn't connect to internet but still able to see local network.
By checking the debug token, the problem seem to be
[ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✗] Failed to resolve via localhost (127.0.0.1)
[✗] Failed to resolve via Pi-hole (192.168.0.155)
But i dont understand what problem is this. What does it mean that it failed to resolve via localhost.
Second problem is that
[✗] lighttpd daemon is failed
However I'm still able to access the pihole web management page so I'm not too worried.
I really dont understand the problem here, was it because I have Nextcloud installed and it causes some issue?
[80] is in use by apache2 (https://docs.pi-hole.net/main/prerequisites/#ports)
*:443 apache2 (IPv6)
[80] is in use by apache2 (https://docs.pi-hole.net/main/prerequisites/#ports)
It failed because there is no domain from the gravity it can query. The database is empty because you deactivated all adlists
1: Because apache is bound to port 80 already
A: So does it caused that I cannot browse the internet?
2: 'It failed because there is no domain from the gravity it can query. The database is empty because you deactivated all adlists'
A: I basically just dont know what else to do/try therefore i disable the adlist to see whether internets come back or not. which failed.
3: 'Your router does not advertise your Pi-hole as DNS via DHCP. Is this on purpose?'
A: Yes, otherwise i wouldn't have internet access.
I follow your advise turn back on the adlist and set my pihole as primary DNS on router (It wouldn't allow me to force only primary dns + secondary dns wouldn't allow me to use the same address as well), it will force other ISP DNS for me on secondary DNS. But still the same, once i set pihole dns as the primary one, entire home internet goes down. What should i do next? New Pihole Debug Log
Sorry ya @yubiuser weekend i do not have access to office network, luckily you do not also reply me on weekend, just to kindly ask is there any other troubleshooting steps i can do? Thanks!
Im not quite sure what those query means. But i dont think it works. Because whenever i specifically specify my PC's lan network dns server to be the pihole server then i wouldn't have any internet connection, but if i let auto config then my internet connection comes back which i believe it invoke the secondary DNS, where i believe at this point it wouldn't go through Pihole so therefore no query will be listed?
Above are some snap shots on my router setting, not sure if it's relevant but i do not know how to check whether i block DNS queries on the router level, is there any specific terms i should look in my router setting page?
hpserver you mentioned above was actually the Pihole device itself.
I still think the network did not route through the pihole, because i have 10 plus pc in my office and the query just look way too low. I then went to Pihole Web Interface -> Tools -> Network.
I only have 1 device are using pihole which is localhost 127.0.0.1::1 (152 queries) which i believe it was the router??
Another is hpserver 192.168.0.155 (13 queries) which is pihole server itself but pihole doesn't know whether or not this device uses pihole.
Your nslookup results show that DNS requests for local (pi.hole) as well as public (google.com) domains time out, even if targeted directly at Pi-hole at 192.168.0.155.
This would indeed suggest a firewall interfering, preventing Pi-hole from receiving the DNS requests or discarding its answers.
Please repeat the nslookup commands and monitor if those requests do register in your Pi-hole's Query Log.
If they don't register, please verify that your Pi-hole host machine's firewall isn't blocking Pi-hole's required ports.
If those nslookups do register and/or all required ports are accessible on your Pi-hole host, then that would suggest your router is blocking DNS traffic.
If you cannot find any router settings related explicitly to blocking DNS/port 53 on your local 192.168.0.0/24 network, you'd have to consult your router's documentation and suppport channels.
For a start, you could try to find out whether that Anti-spoof Checking would prevent local handling of DNS requests.
Sharing your router's make and model as requested by yubiuser may help to attract users with relevant similar experiences.
Omg, Thank you so muchh for reminding!! I just went and check my Ubuntu UFW and just try my luck by allowing port 53 and it's now working! I have no idea because i didn't saw in the documentation that we need to specifically allow it. I appreciate it so so much!
Oh geez, i feel like a complete idiot after knowing that's the issue. Thanks for @yubiuser for staying with me for so long, i almost gave up if it wasn't you that keep replying me.
