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, apache2 or another reverse proxy, or there is some other aspect of your install that is customised) - please use the Community Help category.
Expected Behaviour:
Devices connecting to internet using pihole IP as DNS
Actual Behaviour:
Currently I use Eero in bridge mode connected to an Arris Modem/Router to connect to the internet. I set up pihole a few days ago and my computer it is set up on seems to be connected to the internet, I can ping google etc. I can also ssh into it from devices on the network. I have tried to manually set up my desktop to use the pihole's IP for the DNS server. However, when I do that I have no internet connectivity on my PC, or any other device when I try to set the DNS server manually (such as on my phone). I have tried it network wide by setting the DNS server in my router, but that just ends up with a situation where no devices can connect to the internet.
That is correct and right now the arris modem is the DNS server. If I try to change it to the pihole IP then all the devices no longer have internet access.
Sure. I just tried that on my desktop using the pihole as the DNS. When I tried pinging it I got 4 packets sent and 4 received, so that appeared to work. But when I did the nslookup you suggested the result was that the DNS request timed out.
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.0.18
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
Nothing shows up in the query log. This is what the network overview shows when I log into the pihole admin. Is the localhost the desktop pc that I am trying to run the command from?
Together, this would indicate that something is interfering with DNS in your network.
That could be a firewall on your Pi-hole machine that blocks port 53, see also Prerequisites - Pi-hole documentation.
Or something is intercepting and redirecting DNS requests in your network or at least on the client issuing the nslookup.
The most likely candidates are router-side features like ad-blocking, client isolation or parental control, or some client-side antivirus feature on that Windows client, e.g. AVG Secure DNS or AVAST Real-Site.
