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

    DNS lookup not working

    Scheduled Pinned Locked Moved DHCP and DNS
    4 Posts 3 Posters 3.9k 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.
    • W Offline
      warnerk
      last edited by

      I have a setup with a fixed ip on WAN and 1 LAN. I entered 4 ip adresses as dns servers (1st one 8.8.8.8) on system -> general setup -> dns servers. I have the gateway set to none.  I don't have dhcp enabled.
      Has anyone an idea to fix this problem?

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

        Are you able to ping 8.8.8.8 from pfSense and from a computer in the network? Are you setting the DNS server setting to your pfSense LAN ip address?
        Have you adjusted any FW rules in the LAN tab?

        1 Reply Last reply Reply Quote 0
        • W Offline
          warnerk
          last edited by

          I can ping 8.8.8.8 from the pfsense firewall as well as from any pc. DNS is working on all pc's in my network, only not from the firewall.
          In system-> general setup I have set 4 dns servers. The dns settings on all other computers in my network use my own dns servers and these use 127.0.0.1 or 8.8.8.8, not the firewall.
          I have 4 rules added: tcp 25 outbound only by my mailserver disabled for all others. same for port 465. last rule is allow LAN to any rule.

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

            "I have 4 rules added: tcp 25 outbound only by my mailserver disabled for all others. same for port 465. last rule is allow LAN to any rule."

            Lets see these rules - because the way you describe them, they are not going to work if your last rule is an allow all.

            So you have pointing to itself with the 127.0.0.1 entry - are you running the dns forwarder?  If not what is running on pfsense to resolve, so 127 is should not be there.

            If your not running the forwarder, then you should put a check next to the box that says
            Do not use the DNS Forwarder as a DNS server for the firewall

            And that 127 entry should go away.

            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
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.