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

    Problem using BIND as a secondary DNS

    Scheduled Pinned Locked Moved DHCP and DNS
    1 Posts 1 Posters 238 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.
    • B
      bp81
      last edited by

      I configured our internal Windows DNS server to use pfSense's BIND as a secondary DNS server. BIND on pfSense can forward as expected, but when I try to resolve an internal hostname for the zone that BIND is setup as a secondary for, the error I get from nslookup is "server failed".

      I tried this exact same setup on an Ubuntu Server running as a VM. Installed BIND, worked perfectly, so something seems off with the pfSense implementation of BIND. Looking for solutions, I have reasons I'd like to run BIND on my pfSense boxes.

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