Actually once I switched fully to unbound + DNSSEC only, I had a new issue. At the same times, unbound would stop working. The service would be running, but it wouldn't resolve anything until I restarted the service.

I finally found a common thread for that happening. It almost always directly followed someone doing a lookup of

ns3.csof.netThe IP for those are in the 195.22.x range that was mentioned earlier.

Almost without fail, trying to access one of those, causes unbound to stop working until I restart the service.

If someone is willing to look at that, because of how it lines up, it looks like trying to access/doing a lookup on those domains will either cause the blank pages and lolcat certs, or will cause unbound to stop resolving until the service is restarted.

Unbound in resolver mode? That makes no sense. The deal is is that makes it pretty much impossible to affect everything. They have to target specific name servers for specific domains (or .com, or . (root) etc..

What DNS servers are you handing out to your clients? Running unbound means nothing if your clients are going to 8.8.8.8 / 8.8.4.4 for DNS.

Want an easy way to find out? Block TCP/UDP 53 on LAN to everything but your unbound and see what breaks. Or pass with logging and see what's logged....

After you properly set up DNS and DNSSEC, you still have to clear DNS cache on each client and also have to make sure your clients are not infected with something or running some stupid browser add-on that hijacks things.

So far happened only one time for me.After enabling dnssec and disabling all the forwards to public dns servers it seems to be fixed.In addition, I've created a floating rule to block every local subnet to that 195.22.0.0 range.

Will keep you updated.To be honest the strange thing is that in a couple of years of pfsense pre-2.2 and dnsmasq this never happened.The problem appeared straight after upgrading to 2.2 and dnsresolver even tho, once again, only happened one time so far to me.

I'd certainly investigate the LAN for possible infection. Just look at the amount of malicious crap associated with that IP:https://www.virustotal.com/en/ip-address/195.22.26.248/information/If you have some ISP-supplied router/modem in front of the pfSense box, Google for possible well-known firmware exploits as well.ng DNSSEC most certainly does NOT help anything. Very broken idea.

Thanks for the suggestion, yes, I will try to have a look on this, but the network device (VDSL Bridge Zyxel P-870M) is in bridge mode, so I have no way to connect directly to it (or only via a serial console, with a cable to be found yet). Newest Firmware = 2009.

It just happened again a few minutes ago (3rd time today).

I was also trying to see if the root-servers file was tempered anyhow, but /etc/unbound/root.hints does not exist at all on the pfsense router.

Log extract when problem is happening, with many requests to "ns*.csof.net" servers where it shouldn't be the case :