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

DNS forwarder between VLANs

Scheduled Pinned Locked Moved DHCP and DNS
3 Posts 2 Posters 485 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
    Phatsta
    last edited by Mar 13, 2019, 1:11 PM

    A customer has several VLANs, lets call them;
    company.lan (VLAN1)
    staff.local (VLAN100)
    equipment.local (VLAN200)

    We're using PFsense and DNS forwarder which is working great within each respective VLAN. However, I'd like to resolve DHCP addresses between the VLANs too. For example, I have several switches on VLAN1 (for example 'sw01.company.lan') that I'd like to access from VLAN100 by using name 'sw01'. This does not work today, I have to use name and domain part, as such; 'sw01.company.lan'.

    Is there a way to do this without naming the networks the same?

    1 Reply Last reply Reply Quote 0
    • J
      jimp Rebel Alliance Developer Netgate
      last edited by Mar 13, 2019, 2:08 PM

      You can setup search domains on the clients to try the other domains. That's all up to the client, though. You can add search domains in the DHCP server settings but not all clients respect that. For example, Windows clients won't honor the search domain list from DHCP.

      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

      Need help fast? Netgate Global Support!

      Do not Chat/PM for help!

      P 1 Reply Last reply Mar 13, 2019, 2:19 PM Reply Quote 0
      • P
        Phatsta @jimp
        last edited by Mar 13, 2019, 2:19 PM

        @jimp said in DNS forwarder between VLANs:

        You can setup search domains on the clients to try the other domains. That's all up to the client, though. You can add search domains in the DHCP server settings but not all clients respect that. For example, Windows clients won't honor the search domain list from DHCP.

        Ah, nice. Didn't think of that. I think there's a way to get Win clients to listen to search domains through the domain controller, I have a faint memory of doing that in the past. Cheers mate!

        1 Reply Last reply Reply Quote 0
        3 out of 3
        • First post
          3/3
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
          This community forum collects and processes your personal information.
          consent.not_received