I'm realizing I could go on and on, but I guess the answer is going to be specific to the features you need. On the other hand again, pfS has pfBlockerNG and there is no direct equivalent to it on OPN. Delete both OpenDNS servers we used for initial testing DNS Server 1: 10.4.0.1, VPNWAN Allow DNS Server list to be overridden by DHCP on WAN. Kids are being filtered by OpenDNS as desired. pfBlockerNG is filtering ads as desired on LAN1. On pfSense, I have configured pfBlockerNG to filter ads using DNSBL. I have a Dynamic DNS set up for OpenDNS in pfsense 2.4.3 development version (2.4.3-DEVELOPMENT (amd64) built on Mon Dec 25 23:35:).
Of course, if pfSense is updated, there should be an updated support article to match. My setup has changed pretty significantly from my original pfSense guide and I wanted to update it reflect some of those improvements. On the Guest/Kids network I have configured specific clients (kids computer/tablets) via DHCP to use OpenDNS for various filters. OpenDNS Dynamic DNS Not Working (SOLVED) I'm not sure when this started, but I think at a minimum several months ago, based on the IP that OpenDNS had for me. Please do not open OpenDNS Support tickets about. For questions about how DNSCrypt works, or any specifics about troubleshooting or installation, the DNSCrypt community is the place to go. It won't accept the needed entry in the Hostname field. OpenDNS hosts a community forum where questions about DNSCrypt can be asked and answered by the community members. If you want to get traffic insights out of the firewall, OPN has a nice Netflow setup that pfS lacks, and I also like that OPN has a dnscrypt-proxy package. However, if you read further, I mention that OpenDNS has changed since then and it doesn't appear that pfSense itself has kept up. And the OPN concept of grouping multiple physical interfaces together as a type of virtual interface that can be used in firewall rules is really useful. As an example going the other way, I think that HAProxy configuration is significantly better on OPN than pfS.
For instructions on how to do this, choose your device type from one of the categories below. Traffic shaping, for instance, is more intuitive to configure on pfS since it's integrated into the firewall ruleset, whereas with OPN it's a totally separate ruleset with a totally different UX. To get started, you’ll need to set up one or more of your devices to use OpenDNS’s DNS nameservers. In general, OPN has a better UX model, but that is subjective and there are still some areas where pfS is better. They both have their strengths and weaknesses. I think they're about the same on that front, although things are organized differently between the two so it's difficult to make a direct comparison. I don't think I would agree that pfS has more configuration options. If you are using DHCP on pfSense then let it do its default thing - it will give the clients the pfSense interface IP as the DNS, and pfSense DNS is in forwarding mode to those. Put the special DNS servers in System->General. I'm currently running OPN but have used pfS extensively as well. b) If DNS Resolver is enabled - then select the checkbox to 'Enable Forwarding Mode'.