Expected Behaviour:
New Windows 11 HP laptop should be behaving like all of the other devices on my network.
Actual Behaviour:
One of my PC's (new HP Laptop - Windows 11) can't access the internet when connected to my Pihole. All of my other devices on my network seem to be working fine though. The Laptop may briefly access the internet at times, but for the most part, the PC can't reach anything on the internet.
Setup:
ip of Pihole: 192.168.1.15
ip of WIFI Laptop that won't connect: 192.168.1.250
Pihole WebGUI settings:
Unbound is also setup and showing no errors.
No upstream DNS servers selected in Pihole WebGUI.
Custom IPV4 DNS entry set to 127.0.0.1#5335 Pihole WebGUI.
I have a Unifi DMPro with 3 Vlans so I have the "respond only on interface eth0" selected in Pihole WebGUI
Unifi Dream Machine Pro router settings:
DHCP DNS Server entry set to 192.168.1.15 for Default, Iot, Guest and Other VLAN networks.
Firewall rules in Unifi Dream Machine Pro set to handle VLAN's:
Allow all established and related traffic
Allow Default network to all VLANS
Allow IoT network to Pihole on ports 53,5335 (TCP/UDP)
Allow Guest network to Pihole on ports 53,5335 (TCP/UDP)
Allow Other network to Pihole on ports 53,5335 (TCP/UDP)
Block all other Inter VLAN connections
Again, all of my other MANY devices seem to be working and functioning properly with Pihole. It's just the one Windows Laptop that I'm having issues with.
I'm very new to Pihole and my system has only been setup for about 2 days now. Other than this one issue, everything else seems to be working very well.
Thanks for the reply. I'm away from home now, but actually have my laptop. I connected via VPN using Unfi's Teleport feature that uses a Wireguard tunnel. I did an ipconfig/all like you said and the pihole does show up as the DNS server. The ip for the VPN was 192.168.2.2 However, the VPN connection wouldn't allow me to access the internet. I decided to make some firewall rule changes. I removed these following firewall rules:
Allow IoT network to Pihole on ports 53,5335 (TCP/UDP)
Allow Guest network to Pihole on ports 53,5335 (TCP/UDP)
Allow Other network to Pihole on ports 53,5335 (TCP/UDP)
and replaced them with one rule:
Allow VLANS/VPNS group to Pihole on ports 53, 5335 (TCP/UDP)
I created one group with the following subnets to my VLANS and VPN:
192.168.2.0/24 (VPN)
192.168.10.0/24
192.168.20.0/24
192.168.40.0/24
I'm actually able to connect to my Pihole Web GUI, but the connection is VERY slow. Will have to try this when I get home.
I think I may have figured it out. Simply put, I set up another Pihole on another Rasberry Pi that's exactly like the first one. My Laptop works fine using this Pihole as a DNS server. The only thing I can think of that fixed it is the command I used when installing Pihole. The Youtube video I watched for the first Pilhole said to use this command:
curl -ssl https://install.pi-hole.net | bash
Nope. That wasn't it either. I'm sure I have a faulty Rasberry Pi 4 board or an sd card issue. Tried reinstalling Pihole, but I was having a lot of connection issues. I'm guessing something faulty with the ethernet adapter. I tried various cables and ports on my switches.
I very much doubt that, as the first command is the correct one - the installation script takes care of employing sudo powers when required (see also Installation - Pi-hole documentation).
On the contrary, using sudo may have unintended side effects.
Also, installation would affect Pi-hole as a server, and that offers no explanation why only one client fails.
If it's just that one client that fails, that would be quite a strong indication that something is off with that specific client.
Your debug log looks normal, apart from a foreign key failure in your long term query database.
This would be unrelated to your issue, but let's check whether that would be still present.
What's the output of:
Ok. Not exactly sure what I need to do with that command. And is a quotation missing at the very end? I tried running it but didn't see any output. (EDIT - I see the quotation there now. I don't think it was there first. I didn't see it after copying it using the clipboard icon and pasting it}
I appreciate the help. I honestly think my raspberry pi is faulty though. I had a heck of a hard time trying to reinstall Pihole on that device because while trying to run commands through ssh, I kept losing connection to the device.
My 2nd pihole seems to be working fine though. No problems at all with it and the hardware and components to it are exactly the same as the one I'm having trouble with. From my laptop, I can connect to the Web GUI to the 2nd pihole, but not the first pihole I'm having trouble with. I can't even ssh into the first pihole from my laptop, but I can to the 2nd pihole. What's weird though is that I can connect to the faulty pihole from other devices such as my android phone.
Like I said though, I noticed right away when trying to reinstall Pihole on the first device that something wasn't right because I kept losing connection to it. The first installation on my 2nd pihole device went very smooth though. I was totally unable to even use the Internet on my laptop until I got the 2nd pihole setup and entered it's ip into my router's secondary DNS server setting.
Thanks. And I found another possible problem. I had tried installing Pihole on my Unraid server a couple of weeks ago using a custom ip of 192.168.1.15, but had a lot of issues with it. I thought I had disabled it to mess with it at a later time, but I decided just this week to install Pihole on one of my Raspberri Pi's under the same ip address. I went into my Unraid server today and saw that it was still enabled. I'm guessing that's why I was having so many connection issues with that Pihole installation.
