Does your ISP support IPv6 upstream:
If not, I would disable anything IPv6 related on the router LAN side to avoid those headaches.
EDIT: ow and when configuring conditional forwarding, make sure your router is not configured to use Pi-hole for upstream DNS resolution (WAN/Internet DNS settings) or else you might create a DNS forwarding loop that is not desired.
Nope IPV6 isn't supported
I would suggest to disable anything IPv6 related on the router LAN side settings, and have the clients dis and reconnect from/to network to have these changes propagate.
Do the nslookup test to see if your router can resolve LAN IPv4's to names.
And if so, configure conditional forwarding in Pi-hole (read the warning I posted in my posting above).
pi@yup:~ $ nslookup
nslookup 192.168.1.160 192.168.1.5
Server: 1.1.1.1
Address: 1.1.1.1#53
** server can't find nslookup: NXDOMAIN
192.168.1.160
** server can't find 160.1.168.192.in-addr.arpa: NXDOMAIN
Not sure why it's saying 1.1.1.1 since I use Quad9 not Cloudflare anymore.
Router handles DHCP, DHCP is off on the pi and IPV6 isn't supported with my ISP.
Should I proceed with the conditional forwarding?
I dont believe 192.168.1.5 is your router am I correct?
Probably you should test with below:
nslookup 192.168.1.160 192.168.1.1
192.168.1.5 is PI hole.
Ok will try this thank you I know 192.168.1.1 is router
Server: ttrouter
Address: 192.168.1.1
*** ttrouter can't find 192.168.1.160: Non-existent domain
Is this an IP of a client thats currently connected (has an active DHCP lease)?
If so, your out of luck and cant use conditional forwarding to get client IP's resolved to names and vice versa.
EDIT: other option is to disable the DHCP service on the router and activate the one on Pi-hole as a replacement:
192.168.1.160 is my Computer address which uses ethernet don't think that matters though.
Lease Obtained. . . . . . . . . . : 10 May 2021 17:11:43
Lease Expires . . . . . . . . . . : 11 May 2021 17:33:02
After doing /ipconfig all
Thats an active lease so only (proper) option left is the DHCP server swap to get names and IP's resolved for your LAN.
So change DHCP here to STATIC?
Or just enable DHCP on pi hole
Am not sure but it looks like you've posted a screenshot of the routers own DHCP client section.
It says on top "Internet Connectivity".
You shouldn't touch these settings as the router is also functioning as a DHCP client to acquire IP details from your ISP (like your public IP address on the Internet).
You should look for a LAN DHCP service/server section on the router that needs disabling.
And when want to switch, best to enable the one on Pi-hole first before disabling the one on the router.
EDIT: change the "Manually specify DNS" option back to default acquiring DNS servers from your ISP in the "Internet Connectivity" section.
That way if Pi-hole dies for some reason, you only have to enable the DHCP service on the router again to have everything working again without Pi-hole.
Ok disabled DHCP on router settings, changed the DNS to automatic and will test if that works with pi hole now by inputting 192.168.1.5 aka my raspberry pi
Almost.
In the "Internet Connectivity" settings, I would change the field named "DNS" from "Manually" into something like "Automatically from ISP".
Once you have configured and enabled Pi-hole's own DHCP service, you grab that Windows client and renew the DHCP lease by running below in a command prompt:
ipconfig /renew
And see what DNS server(s) are configured now on that client with below one in that same command prompt:
netsh interface ip show dnsservers
Or check below to see from who the lease is coming from (the "DHCP Server" line):
ipconfig /all
And test DNS resolution with nslookup eg:
C:\>nslookup pi.hole
Server: ph5a.home.dehakkelaar.nl
Address: 10.0.0.2
Name: pi.hole
Address: 10.0.0.2
C:\>nslookup pi-hole.net
Server: ph5a.home.dehakkelaar.nl
Address: 10.0.0.2
Non-authoritative answer:
Name: pi-hole.net
Address: 178.128.134.214
Test blocking:
C:\>nslookup flurry.com
Server: ph5a.home.dehakkelaar.nl
Address: 10.0.0.2
Name: flurry.com
Addresses: ::
0.0.0.0
Or my laptop client:
C:\>nslookup laptop
Server: ph5a.home.dehakkelaar.nl
Address: 10.0.0.2
Name: laptop.home.dehakkelaar.nl
Address: 10.0.0.220
I haven’t attempted any of that but everything i’ve done has done this so far and more keep getting added so i believe it’s working?
Seems Pi-hole can resolve IP's to proper names now for your DHCP clients (the clients advertise their name to the DHCP server when getting a lease).
Wait a bit until all clients have renewed their DHCP lease before the old lease from the router is about to expire (can take 24 hours).
Or power cycle them to have them renew their lease immediately.
To properly test, you would need to run those nslookup tests to be sure.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.
