Pihole is installed on a Raspberry PI A+ that is connected to the network via a usb (gadget mode).
Expected Behaviour:
After adding the pihole ip as the DNS on my Windows machine then hosts should still resolve and be reachable via a browser.
Actual Behaviour:
No pages can be reached when using a browser. The DNS resolves when using nslookup but hosts cannot be pinged.
PS C:\Users\_> nslookup pi-hole.net
Server: raspberrypi
Address: 192.168.137.133
Non-authoritative answer:
Name: pi-hole.net
Addresses: 2604:a880:400:d0::1071:1
206.189.252.21
PS C:\Users\_> ping pihole.net
Ping request could not find host pihole.net. Please check the name and try again.
Debug Token:
https://tricorder.pi-hole.net/xq8r15q07a
Oops, well spotted. Even so I will get the same result with any domain I ping.
i.e pi-hole.net
PS C:\Users\_> ping pi-hole.net
Ping request could not find host pi-hole.net. Please check the name and try again.
EDIT: I still can't ping via domain names but I can actually ping 8.8.8.8 and 8.8.4.4
Sure, I got a request time out
Pinging 206.189.252.21 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 206.189.252.21:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Sorry, I have pings disabled on that server. Try pinging an outside DNS server, ping 9.9.9.10
And does nslookup pi.hole
work? Are you removing the last two digits of that Address: line? (You don't need to, that's a private IP address range that can't route over the internet anyways.)
Ah, I was editing those last digits. I have editied the post to add them back in.
Here are the results:
Pinging 9.9.9.10 with 32 bytes of data:
Reply from 9.9.9.10: bytes=32 time=29ms TTL=55
Reply from 9.9.9.10: bytes=32 time=30ms TTL=55
Reply from 9.9.9.10: bytes=32 time=31ms TTL=55
Reply from 9.9.9.10: bytes=32 time=30ms TTL=55
Ping statistics for 9.9.9.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 31ms, Average = 30ms
PS C:\Users\_> nslookup pi.hole
Server: raspberrypi
Address: 192.168.137.133
Name: pi.hole
Addresses: fe80::502e:877e:899f:ab86
192.168.137.133
The debug log is okay, I don't see anything there. The Pi-hole is responding correctly as well. Can you ping pi.hole
?
Odd. I can't: Ping request could not find host pi.hole. Please check the name and try again.
Check ipconfig /all
and make sure the only DNS listed is the Pi-hole IP address.
Example:
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physical Address. . . . . . . . . : 00-D8-61-9C-E6-D4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.88.254(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, April 14, 2020 6:11:49 PM
Lease Expires . . . . . . . . . . : Saturday, April 18, 2020 6:07:00 PM
Default Gateway . . . . . . . . . : 192.168.88.1
DHCP Server . . . . . . . . . . . : 192.168.88.1
DNS Servers . . . . . . . . . . . : 192.168.88.2
NetBIOS over Tcpip. . . . . . . . : Enabled
Here is the output of ipconfig /all. "Ethernet adapter Ethernet 2" is my enabled ethernet connection which is sharing its connection with "Ethernet adapter Raspberry Pi USB" .
Windows IP Configuration
Host Name . . . . . . . . . . . . : _
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I219-V
Physical Address. . . . . . . . . : 40-8D-5C-BF-79-6D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Ethernet 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) I211 Gigabit Network Connection
Physical Address. . . . . . . . . : 40-8D-5C-BF-79-6B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::609f:f78:7d52:7d0e%28(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.107(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 19 April 2020 10:47:51
Lease Expires . . . . . . . . . . : 20 April 2020 11:45:07
Default Gateway . . . . . . . . . : fe80::60c1:1bff:fecd:7f76%28
192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 306220380
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-77-CF-82-40-8D-5C-BF-79-6D
DNS Servers . . . . . . . . . . . : 192.168.137.133
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Raspberry Pi USB:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : USB Ethernet/RNDIS Gadget
Physical Address. . . . . . . . . : 12-92-88-1A-BC-AA
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::1a1:c4fa:197a:40f1%24(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.137.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 1065516757
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-77-CF-82-40-8D-5C-BF-79-6D
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Wireless LAN adapter WiFi:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 8260
Physical Address. . . . . . . . . : A4-34-D9-A2-0D-D2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Local Area Connection* 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : A4-34-D9-A2-0D-D3
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Local Area Connection* 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physical Address. . . . . . . . . : A6-34-D9-A2-0D-D2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Bluetooth Network Connection 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network) #2
Physical Address. . . . . . . . . : A4-34-D9-A2-0D-D6
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch):
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter
Physical Address. . . . . . . . . : 00-15-5D-D7-C6-E2
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::9dda:1473:c55d:a4b4%39(Preferred)
IPv4 Address. . . . . . . . . . . : 172.17.161.65(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 654316893
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-77-CF-82-40-8D-5C-BF-79-6D
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
That's the IP for the pi hole. I think 192.168.137.1 is the gateway?
jfb
April 19, 2020, 1:06pm
14
Although you are sharing an ethernet connection, I don't think the DNS resolution will jump ranges. The PC is one IP range (192.168.1.x), the Pi-hole is on another 192.168.137.x).
Thanks, that didn't even occur to me. So are you suggesting the address for the PI should look something like 192.168.1.X so that pihole assigns addresses in that range?
I've tried reassigning the IP to the address 192.168.1.54 (which is below the router assigned addresses which between 192.168.100 - 192.168.199) but when I do that it appears that any network connectivity on the pi fails. Could it be because this is via a usb0 connection? It seems strange that 192.168.137.133 was given to pihole by DHCP when I first set it up.
system
Closed
May 10, 2020, 6:10pm
16
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.