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

    DHCP lease update in DNS

    Scheduled Pinned Locked Moved DHCP and DNS
    3 Posts 3 Posters 859 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.
    • D Offline
      doejohn
      last edited by

      Hello,

      I have a problem with dynamic DNS updates of DHCP host names.

      I can see the host names on the "Status/DHCP leases" page. But the DNS forwarder won't resolve until I restart the DNS service (or reconfigure something, so the service is restarted).

      When waiting long enough (several hours?) the update happens eventually. But since DHCP and DNS are served by the same process (dnsmasq), I'd expect the update to happen immediately. At least this is what I was used to, when I used dnsmasq directly on linux some years ago.

      Any ideas?

      PS: I am using pfSense-2.1.5-RELEASE-4g-i386-nanobsd.img.gz

      1 Reply Last reply Reply Quote 0
      • N Offline
        neik
        last edited by

        @doejohn:

        Hello,

        I have a problem with dynamic DNS updates of DHCP host names.

        I can see the host names on the "Status/DHCP leases" page. But the DNS forwarder won't resolve until I restart the DNS service (or reconfigure something, so the service is restarted).

        When waiting long enough (several hours?) the update happens eventually. But since DHCP and DNS are served by the same process (dnsmasq), I'd expect the update to happen immediately. At least this is what I was used to, when I used dnsmasq directly on linux some years ago.

        Any ideas?

        PS: I am using pfSense-2.1.5-RELEASE-4g-i386-nanobsd.img.gz

        I am having exactly this problem with 2.2.2

        1 Reply Last reply Reply Quote 0
        • P Offline
          pericynthion
          last edited by

          Also seeing this.  Using 2.2.2.  Any hints for debugging?
          Sometimes a new DHCP client will register ~instantly in the DNS, others take many minutes or never show up at all.  It doesn't seem to be particularly tied to a given MAC.  Restarting Unbound will cause them all to register.

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