Pi-hole 4.0 + Unbound WORKING with IPv6, COX Internet, and DD-WRT w/ DNSSEC Enabled

So, I finally got my system working 100%, and figured I'd share my setup so MAYBE I could help others.

Hardware:
Motorola Surfboard DOCSIS 3.0 Modem
Linksys EA8500 with custom DD-WRT installed
RaspberryPi 3B with Raspbian Lite Stretch and Pi-Hole 4.0 W/Unbound

On router I have:

Use DNSMasq for DHCP enabled
Use DNSMasq for DNS enabled
DHCP-Authoritative disabled
Recursive DNS Resolving disabled (caused huge problems with Pi connecting, but internet works)
Forced DNS Redirection disabled
Both IPv4 and IPv6 DNS settings pointing to Pi-hole
DHCP automatically assigning IP addresses via router

On RaspberryPi I have:

Unbound installed as per Pi-hole Blog W/ IPv6 Enabled in Config file (Used NANO command to edit the file)
Pi-hole 4.0 installed as per Blog
DNS Settings pointed at google on install, however adjusted to custom after installation.
DNS IPv4 custom pointing only to 127.0.0.1#5353 (Unbounds port on localhost)
DNS IPv6 custom pointing to ::1#5353 (Unbounds port)

With this setup I'm running smooth. Tested results via:

Test Adblock: Pi-hole.net ad block test page and fivefilters.org test (also located on pi-hole.net test page)
[Mod Edit: Link no longer available]

Test Unbound: dnsleaktest.com should report back your home IP address only on extended test. Note: This setup IS NOT a secure way to hide like VPNs.

Test IPv6 and DNSSEC: internet.nl (Netherlands government website). If DNSSEC fails, goto your command line if windows and do an "ipconfig /flushdns" and restart your browser. another good resource for testing/troubleshooting DNSSEC is https://dnssec.vs.uni-due.de/

If you have questions, feel free to ask and I'll try and help.

1 Like

I do not have IPv6 as an option at this time on my router (Gargoyle firmware)

What issues were you seeing with these other options enabled? I currently have pi-hole setup as a list dhcp_option '6,xxx.xxx.x.xxx' within my /etc/config/dhcp this will show all names and ips of devices using my pi-hole.

I have always had issues with unbound being recursive in that some domains will not resolve, but will using cloudflare, I simply get a nxdomain within unbound.

Did you have these issues? If so, did these router settings fix this issue? I think a big problem I am having is some cdn's do not see that I do not resolve ipv6 so I get a ipv6 address that also fails I have do-ip6: no

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