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

DHCP Server - Domain search list

Scheduled Pinned Locked Moved DHCP and DNS
5 Posts 3 Posters 3.2k 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.
  • G
    gschreiber
    last edited by Jun 6, 2017, 1:35 PM

    Hi,

    I´m running pfsense CE 2.3.4-RELEASE and configured this as "DHCP-Server - Domain search list":

    domain1.com; domain2.org

    As the manual says, separated with semicolons  :)

    Now my DHCP-client (CentOS 6) generates this resolv.conf:

    search domain1.com. domain2.org.

    think this shoud be right: search domain1.com domain2.org
    Is this a pfsense or centos problem?

    kind regards,
    Georg

    1 Reply Last reply Reply Quote 0
    • G
      gjaltemba
      last edited by Jun 6, 2017, 2:21 PM

      Have you tried adding trailing semicolon?

      domain1.com; domain2.org;

      Check the output of

      cat /var/dhcpd/etc/dhcpd.conf

      to verify if the problem is pfSense.

      1 Reply Last reply Reply Quote 0
      • K
        kpa
        last edited by Jun 6, 2017, 2:33 PM

        Is it a real problem? The trailing dot is usually taken as a terminator that simply means the root (.) domain and it shouldn't make a difference in the search domains if it is there or is missing.

        1 Reply Last reply Reply Quote 0
        • G
          gschreiber
          last edited by Jun 6, 2017, 2:55 PM

          ok,

          with configured list

          domain1.com; domain2.org

          cat dhcpd.conf is

          option domain-search "domain1.com","domain2.org";

          -> looks correct afaik…

          1 Reply Last reply Reply Quote 0
          • G
            gschreiber
            last edited by Jun 6, 2017, 3:49 PM

            I captured the DHCP-Packet, so its no problem with pfsense  :)

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