Can't Browse To Websites Using Pihole, though Pihole Resolves DNS

Evessal · October 12, 2019, 2:53am

Please follow the below template, it will help us to help you!

Expected Behaviour:

Pihole setup on Windows initially with Docker, then Ubuntu VM on VMWare Workstation (current setup). Successfully resolves DNS. Should be able to browse to websites when NIC card manually is set to IP address of Pihole server.

Actual Behaviour:

I can resolve DNS with Pihole, for instance dns.google resolves to 8.8.8.8 and 8.8.4.4 using the IP address of my Pihole VM. I can ping the Pihole VM from my desktop. However when I manually update my NIC card settings on Pihole to utilize the Pihole as my DNS server, I cannot browse to any website. Admin panel does show hits coming in only from localhost client.

Any help is appreciated.

Debug Token:

1pwblualpu

jfb · October 12, 2019, 2:56am

Your debug log shows that Pi-Hole is working normally.

What OS is on the client you are using to set the NIC settings?

Evessal · October 12, 2019, 3:41am

Hi Jfb

First off, sorry for the typos. That should state that when I update my NIC card settings on the client to utilize Pihole as the DNS server. I'm using a Windows client. If it is of any importance, the client I'm using to test is out is the same device that the VMWare workstation hosting Pihole is running on.

jfb · October 12, 2019, 3:58am

From the same PC, what is the ouput of this command from the command prompt:

ipconfig /all

Evessal · October 12, 2019, 4:12am

Here it is

C:\Users\Ehsan>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-85O9SVC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter vEthernet (Default Switch):

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter
Physical Address. . . . . . . . . : 00-15-5D-4A-7F-3A
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5ab:f6e1:74e8:6b71%9(Preferred)
IPv4 Address. . . . . . . . . . . : 172.18.45.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 369104221
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-25-2D-B1-92-00-25-90-BC-DA-34
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter vEthernet (DockerNAT):

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
Physical Address. . . . . . . . . : 00-15-5D-00-08-0C
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::6d87:f26c:eafe:d6dd%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Connection X722 for 1GbE
Physical Address. . . . . . . . . : 00-25-90-BC-DA-34
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Connection X722 for 1GbE #2
Physical Address. . . . . . . . . : 00-25-90-BC-DA-35
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2606:6000:c300:c400:ccec:e834:f3f1:3be9(Preferred)
Temporary IPv6 Address. . . . . . : 2606:6000:c300:c400:49d1:ddda:a50b:5c74(Preferred)
Link-local IPv6 Address . . . . . : fe80::ccec:e834:f3f1:3be9%21(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.8(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, October 11, 2019 7:34:01 PM
Lease Expires . . . . . . . . . . : Friday, October 11, 2019 9:41:47 PM
Default Gateway . . . . . . . . . : fe80::aeec:80ff:fe30:31b7%21
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 402662800
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-25-2D-B1-92-00-25-90-BC-DA-34
DNS Servers . . . . . . . . . . . : 192.168.50.128
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet1:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
Physical Address. . . . . . . . . : 00-50-56-C0-00-01
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::14e2:4ff4:671d:2de1%17(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.11.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, October 11, 2019 8:41:44 PM
Lease Expires . . . . . . . . . . : Friday, October 11, 2019 9:26:44 PM
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.11.254
DHCPv6 IAID . . . . . . . . . . . : 671109206
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-25-2D-B1-92-00-25-90-BC-DA-34
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter VMware Network Adapter VMnet8:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
Physical Address. . . . . . . . . : 00-50-56-C0-00-08
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::fd3e:8ab:688b:7048%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.50.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, October 11, 2019 8:41:45 PM
Lease Expires . . . . . . . . . . : Friday, October 11, 2019 9:26:45 PM
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 192.168.50.254
DHCPv6 IAID . . . . . . . . . . . : 687886422
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-25-2D-B1-92-00-25-90-BC-DA-34
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Primary WINS Server . . . . . . . : 192.168.50.2
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet 2 is the NIC adapter that connects to my cable modem and gets me out to the internet.

jfb · October 12, 2019, 4:19am

The NIC is at IP 0.8. The DNS server is on a different IP range (50.128). How can the NIC connect to the Pi-Hole at that IP? Do you have multiple VLANS and the Pi-Hole is on a bridged VLAN so the clients on other VLANS can find it?

What is the IP address of the Pi-Hole? If you generate a Pi-Hole debug log and upload it and post the token, we can look at the configuration.

Evessal · October 12, 2019, 4:28am

Oh my... you are right! When I type "ping 192.168.50.128" on the command line, I was getting replies. I totally forgot that it's probably sourcing that from the local NIC adapter... when I typed "ping 192.168.50.128 -S 192.168.0.8".. well guess what, I got transmit failures! You are right, there is no communication. I went ahead and changed the settings on my VM from NAT to Bridge. Got Pihole on an IP address of 192.168.0.9... and voila.. now I'm seeing requests coming from my local client at 192.168.0.8 on the Dashboard!

I was thrown off by the successful ping of 192.168.50.128, thinking that since I could ping it from the command line it should work. Totally forgot about sourcing the ping from the correct NIC. Thank you so much sir! I realize now what is happening.

system · November 2, 2019, 4:29am

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.