Expected Behaviour:
[An ad-free internet]
Actual Behaviour:
[No internet]
Debug Token:
[https://tricorder.pi-hole.net/047e3x96p2 ]
The devices on my local network have difficulty connecting to the internet after I configure my router to use the pi-hole as the DNS server.
jfb
October 4, 2019, 10:29pm
2
Your debug log shows that Pi-Hole is working properly and can receive and process DNS queries arriving at IP 192.168.1.19.
There is likely a configuration problem on the router. If you have a Windows client, what is the output of the following commands from the command prompt:
nslookup pi.hole
ipconfig /all
Hi jfb, thanks for the reply. I manually configured my windows machines to use pi hole as their DNS. Yet, when I set the pi-hole as my DNS on the router, that's when my devices have difficulty reaching the internet.
The pi-hole may have worked for a few seconds after configuring my router to use the pi-hole as the DNS, which is when the log I originally uploaded was generated.
Here's another log,
https://tricorder.pi-hole.net/oq2teed2pm
**>nslookup pi.hole**
Server: UnKnown
Address: 192.168.1.19
Non-authoritative answer:
Name: pi.hole
Addresses: 198.105.244.24
198.105.254.24
**ipconfig /all**
Windows IP Configuration
Host Name . . . . . . . . . . . . : DESKTOP
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : lan
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : lan
Description . . . . . . . . . . . : Intel(R) 82579V Gigabit Network Connection
Physical Address. . . . . . . . . : 54-04-A6-1B-B1-E2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::e4a0:c6ef:edc:f6a9%18(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, October 3, 2019 9:04:04 PM
Lease Expires . . . . . . . . . . : Saturday, October 5, 2019 9:04:03 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.19
DHCPv6 IAID . . . . . . . . . . . : 273941670
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-2E-0E-42-54-04-A6-1B-B1-E2
DNS Servers . . . . . . . . . . . : 192.168.1.19
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Npcap Loopback Adapter:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Npcap Loopback Adapter
Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::3cf0:99a3:8056:28b3%9(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.40.179(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 805437516
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-2E-0E-42-54-04-A6-1B-B1-E2
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 3:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Leaf Networks Adapter
Physical Address. . . . . . . . . : 00-FF-1A-59-79-D6
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::e487:b93a:8fb6:eb42%4(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.235.66(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 520159002
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-2E-0E-42-54-04-A6-1B-B1-E2
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
system
Closed
October 26, 2019, 8:19am
6
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.