Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    (Solved) OpenDNS DNS with Pfsense 2.2.4

    Scheduled Pinned Locked Moved DHCP and DNS
    7 Posts 3 Posters 2.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P Offline
      pistolfire99
      last edited by

      Hello All,

      I am a beginner Pfsense user where my network is as such: (Internet) == (pfsense) == (lan users)

      I wish to use opendns: 208.67.220.123/208.67.222.123 for basic dns filtering.

      I am attaching the screenshot of my setup below. I have also followed the "Blocking DNS queries to external resolvers" guide but still my setup is not working.

      When I visit https://www.opendns.com/welcome/ or internetbadguys.com it says I am not using OpenDNS.

      Not sure what I am missing.

      Thanks,

      Pete.
      pfsense.dashboard.png
      pfsense.dashboard.png_thumb
      pfsense.general.png
      pfsense.general.png_thumb
      pfsense.rules.png
      pfsense.rules.png_thumb

      1 Reply Last reply Reply Quote 0
      • johnpozJ Offline
        johnpoz LAYER 8 Global Moderator
        last edited by

        And are you actually using the forwarder or the resolver?  Not going to use what you put in system dns if your using the resolver which is the new default out of the box with 2.2.4

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 25.07.1 | Lab VMs 2.8.1, 25.07.1

        1 Reply Last reply Reply Quote 0
        • P Offline
          pistolfire99
          last edited by

          I am using the resolver, with "Enable forwarding mode' = Unchecked

          Are you suggesting I use forwarder instead ?

          1 Reply Last reply Reply Quote 0
          • P Offline
            pistolfire99
            last edited by

            Changing from Resolver to Forwarder did the trick.

            Thanks for the 'hint'

            See below attached files for the end result, which is what had been desired.

            opendns.welcome.png
            opendns.welcome.png_thumb
            opendns.bad.png
            opendns.bad.png_thumb

            1 Reply Last reply Reply Quote 0
            • D Offline
              doktornotor Banned
              last edited by

              Yeah, of course. With "Enable forwarding mode' = Unchecked in resolver, unbound just does recursive resolution itself, will never use anything in System - General.

              1 Reply Last reply Reply Quote 0
              • P Offline
                pistolfire99
                last edited by

                @doktornotor:

                Yeah, of course. With "Enable forwarding mode' = Unchecked in resolver, unbound just does recursive resolution itself, will never use anything in System - General.

                Are you suggesting to use 'Resolver' with "Enable forwarding mode = Enabled" ? or just using forwarder sufficies ? My networking needs are simple as of now. I help manage a network in a small hotel/resort with varying userbase and primary criteria is to "Keep a tab on bandwidth by preventing users from accessing porn sites".

                1 Reply Last reply Reply Quote 0
                • D Offline
                  doktornotor Banned
                  last edited by

                  Should work. Though, for this type of usage, the forwarder is just fine. You won't get any DNSSEC validation with OpenDNS anyway.

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.