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

    DNS on VLAN Interface

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 2 Posters 1.4k 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
      pfnewb2016
      last edited by

      Trying to set DNS resolver bound to both LAN and VLAN 200 interfaces; it is bound on LAN and localhost, not active/bound to VLAN200.  DHCP from fw on VLAN 200 interface 192.168.200.1 is working.

      LAN:    192.168.104.1/24

      VLAN 200:    192.168.200.1/24
      VLAN 200 is sub interface of LAN

      Screen shots attached.

      Thanks for your help

      pf_DNS_ResolverSettings1.png
      pf_DNS_ResolverSettings1.png_thumb
      pf_Status_DNS.png
      pf_Status_DNS.png_thumb
      pf_GeneralSettings_DNS.png
      pf_GeneralSettings_DNS.png_thumb
      pf_Interfaces.png
      pf_Interfaces.png_thumb

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

        You already have it bound to your vlan.. Why you have it set like that for outgoing interfaces have no idea?  Do you have downstream name server you need to query?

        If your using the resolver - why do you have 192.168.104.3 and 8.8.8.8??  I could guess that 192.168.104.3 is a downstream name server??  But why googledns as well? To be honest if your using unbound in resolver mode the only dns that should be listed for pfsense is 127.0.0.1

        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 24.11 | Lab VMs 2.8, 24.11

        1 Reply Last reply Reply Quote 0
        • P
          pfnewb2016
          last edited by

          Thanks for your response, this ended up being a firewall rule problem.

          There are internal DNS servers so no need for pfsense DNS on the LAN.  Want to provide 2 DNS servers for the guest wifi: pfsense is primary, google dns is 2ndary.

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

            "Want to provide 2 DNS servers for the guest wifi: pfsense is primary, google dns is 2ndary."

            Why??  If your guest wifi need to resolve stuff on pfsense then if they happen to ask google that will fail.  Normally in a guest setup that you do not have any need for the guest to resolve anything local you would just point them to something outside like google.  So if your worried about google dns failing just point them to opendns as your secondary.  Both of these ns can resolve the same stuff.

            In a scenario where your pointing to pfsense and some public your talking to ns that can not resolve the same stuff which cold cause problems if that different stuff is needed.

            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 24.11 | Lab VMs 2.8, 24.11

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