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

    Unbound/DHCPD Do Not Honor Custom Domain Name set in DHCP Server Config

    Scheduled Pinned Locked Moved DHCP and DNS
    1 Posts 1 Posters 489 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.
    • C Offline
      CampinCarl
      last edited by

      Hello pfSense community. I wanted to confirm if the following is a bug or the intended behavior.

      I've added a GUEST network interface and configured its DHCP Server to use a different domain name ("guest"). The system is configured to register DHCP leases with the Unbound DNS Resolver. For simplicity, let's say my default domain name (General Setup) is "bar", e.g., "foo.bar".

      When performing a DNS query (#host foo) against a host in the GUEST network, the expected response is "foo.guest"; I'm seeing "foo.bar" instead.

      Peeking at the Unbound configuration files reveals that the server is responding "correctly" because foo is registered in the /var/unbound/dhcpleases_entries.conf file as "foo.bar" instead of "foo.guest" as expected.

      It seems that when registering the DHCP lease, either Unbound or DHCPD does not respect the Domain Name setting.

      Is there something simple I'm missing here? If this is the intended behavior, can anyone recommend a custom configuration for either dchpd or Unbound to achieve the desired behavior?

      Any ideas would be greatly appreciated.

      Thanks in advance.

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