I am just having some issues getting DCHP to work and would really appreciate some help.
Expected Behaviour:
Turn off DCHP in BT smart hub 2 and enable it in the PieHole should allow devices to connect to the internet with ads blocked.
Actual Behaviour:
When I have turned off the DCHP setting in my BT smart hub 2 and enabled it in the PieHole no devices can connect to the internet. They cant resolve DNS. I can see devices being assigned IP addresses in the PieHole. I have tried restarting all devices on the network but still no luck.
I have used my PieHole for a while with an older ASUS router but im now in an FTTP house and have to use the BT router at the moment so have no way of using the previous DNS option I used before.
It may be that I am missing something as I have not used DCHP on the PieHole before but ive been around in circles trying to get it working with no avail. Any help would be hugely appreciated. Thank you.
As you say the devices are being assigned IP addresses, make sure that they are able to access Pi-hole and resolve DNS. What is the output of nslookup pi.hole on one of the devices? Is the only DNS in their settings set to Pi-hole?
Hi, thank you very much for getting back to me and apologies for my slow reply. Below I have included the results of nslookup before and after changing the DCHP settings. Hopefully it means more to you than it does to me:
With the DCHP set by the router these are the results
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
Name: pi.hole
Address: 192.168.1.247
These are the properties for the wifi in windows 10 if that helps:
Make sure that you have the correct IPv6 address for the Pi-hole server. The DHCP settings currently use fd9b:894e:ded5:1:b53e:afcf:164a:46c1, but that address does not seem to be working. You may have to use pihole -r to reconfigure the address.
You have a network issue preventing your devices from reaching the Pi-hole server over fd9b:894e:ded5:1:b53e:afcf:164a:46c1. Either use a different IPv6 address that the other devices can use, or fix the issue.
Try editing /etc/pihole/setupVars.conf and change the value of IPV6_ADDRESS to a reachable IPv6 address. Then run pihole -r to repair.
Fixing the current one means routing requests to that address to your Pi-hole server (right now the requests are not making it to Pi-hole). This depends upon how you set up your network, and is beyond the scope of Pi-hole.
I accessed the PiHole through PuTTY tried editing the setupVars. I keep getting access denied even though I have logged in as the main user.
I have also just checked the PiHole though the web interface and gone into settings then system. There is an IPv4 address listed there but the IPv6 is showing no address at all.
Thanks for the help on getting to the point where I can edit the setupVars.conf. I've had a look and IPV6_ADDRESS= shows nothing beside it. If I type in the ipv6 address I want to use how do I then save this?