Receives requests from every user, large domain catalog at 1.3 million, but ads remain visible ðŸ˜
Receives requests from every user, large domain catalog at 1.3 million, but ads remain visible ðŸ˜
So why switch from Pi-Hole to OPNsense? You might prefer unbound in OpenOS because it comes with built-in block lists that can help filter traffic directly. Those lists are designed to block unwanted content without needing extra tools. Just make sure the pages you're testing actually have ads, as they should be filtered properly.
I carried out the actions from the video and experienced a total internet shutdown. Did I make a mistake? Could it be creating a loop that leads to this issue? Steps taken: Turned on Unbound DNS, enabled DNS blocklist, set DNS server IPs accordingly, saved configurations. Verified setup by checking local statistics.
I won't pretend to be an expert. I can simply share what I did and what helped me. I didn’t use that specific setup. I’m also using VLANs, meaning I have multiple VLANs and define everything under each individually rather than grouping them into a single LAN. - There’s no DNS configured for the VLANs (similar to your LAN). - In Settings, I have standard DNS, not from the OPNsense device. (Uses 8.8.8.8 and 9.9.9.9 via WAN) - This means all devices get an IP in their respective VLAN and a DNS address tied to that VLAN. So if a machine gets 192.168.50.2, its DNS will be 192.168.50.1. - In short, it still works the same way, keeps internet access, and blocks ads.
You're trying to confuse things without fully grasping what you're doing. Just edit nothing in Unifi for pihole-related reasons. In your situation, Unifi is just a switching device. The gateway you changed should be your actual gateway—your OPNsense box's IP address. In OPNsense, under DHCP, set the DNS to your pihole IP. This will assign that IP through DHCP to all connected clients, who then use pihole for DNS. I set up my system similarly, and now I point pihole's DNS to my gateway (PFSense). PFSense handles DHCP and acts as your router, providing hostname resolution to pihole. That should clarify things.
I checked your situation carefully. You mentioned running unbound on OPNsense, but you already had it active from a tutorial. After renewing your DHCP lease, your computer lost network access. With a standard router, setting up Pihole worked fine, but OPNsense and Unifi integration is quite different. Did you notice any specific error messages or steps that didn’t go as planned?
I don’t have enough knowledge about Opensense to fully understand that condos page. It seems similar to what your old router would have done. Just provide your Pihole as the DNS in your DHCP settings for each interface (you should have done this correctly). Keep inbound traffic running on Opensense, because Pihole will act as the upstream DNS. I’m not sure what’s wrong, but restoring everything without Pihole in the loop should work again—just point Pihole to the upstream DNS in Opensense and set its IP as the DHCP client address for clients.
This configuration helps maintain a consistent DNS resolution by using PiHole as a reverse proxy. The setup ensures that PiHole handles DNS lookups while OPNSense manages DHCP. If you're relying on PiHole, its DNS settings should point to 1.1.1.1 for optimal performance. Waiting is necessary because DNS entries can cache locally for some time before being refreshed.
I recommend using OPNsense with OPNsense point to 1.1.1.1. This is because OPNsense manages DHCP, so it has access to all connected machine names. Pihole can still be set up manually, though you could use the PFSense approach for a smoother setup. Switching from PFSense to Unifi required moving away from haproxy and setting up Nginx proxy manager. Now Pihole is fully in charge of DNS resolution. In short, both configurations are viable if users understand their setup properly.
I waited five minutes, then checked how to refresh the DNS using the terminal. I tried the code I found and it caused a problem. Before that, I changed settings, selected Wi-Fi, went to advanced options, and clicked "renew DNS." Doing it without the code also led to an issue. I'm now investigating further to understand my mistakes, but I've spent several days assisting my parents.