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

    DNS Resolver doesn't work

    Scheduled Pinned Locked Moved General pfSense Questions
    26 Posts 4 Posters 2.4k Views 4 Watching
    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.
    • O Offline
      orphen76 @stephenw10
      last edited by

      @stephenw10 yes sory on a host.
      below from a clean host:

      nslookup www.google.com
      Server: UnKnown
      Address: 172.16.24.1

      johnpozJ GertjanG 2 Replies Last reply Reply Quote 0
      • johnpozJ Offline
        johnpoz LAYER 8 Global Moderator @orphen76
        last edited by

        @orphen76 said in DNS Resolver doesn't work:

        Server: UnKnown

        that points to a problem to be honest, is that not pfsense? pfsense should always be able to resolve its own name.

        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

        O 1 Reply Last reply Reply Quote 0
        • GertjanG Offline
          Gertjan @orphen76
          last edited by

          @orphen76 said in DNS Resolver doesn't work:

          Address: 172.16.24.1

          That is your pfSense LAN IP, right ?

          And no answer came back ?

          Can you post your LAN firewall rules ?
          Like :

          eb9142a2-535c-44da-9c3a-9cb9a2e89cdc-image.png

          Unbound is listening on the LAN interface ?
          Like :

          83cd7ec7-f259-42cc-ae9a-d42231d77be6-image.png

          No "help me" PM's please. Use the forum, the community will thank you.
          Edit : and where are the logs ??

          O 1 Reply Last reply Reply Quote 0
          • O Offline
            orphen76 @Gertjan
            last edited by

            @Gertjan ![alt text]
            Hi,
            below

            rule.jpg networkinterf.jpg

            GertjanG 1 Reply Last reply Reply Quote 0
            • GertjanG Offline
              Gertjan @orphen76
              last edited by

              @orphen76

              Thanks.
              I've added to the mix : queues and scheduled rules ....

              I hope Google translate will do the job :

              Backup your pfSense config. So from now on, you can go back the what you have right now.

              Then : console menu option 4 - Factory defaults.

              From now on, you have to respect one rule : change only the admin password. Change nothing else.
              I make a special note for DNS : don't remove add change anything. Out of thne box, the resolver works just fine.

              Do some testing and conclude that everything works fine.

              Now, you have a choix :
              Import the backed up config. And then goto here, as you're back to square one.
              Or : add your own changes one by one, each step separated by extensive testing.
              As soon as you detect that something 'fails', you know where it went wrong.

              No "help me" PM's please. Use the forum, the community will thank you.
              Edit : and where are the logs ??

              1 Reply Last reply Reply Quote 0
              • GertjanG Gertjan referenced this topic on
              • O Offline
                orphen76 @johnpoz
                last edited by

                @johnpoz the firewall router to which the workstation from which I ran the command is connected is pfsense

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