Bug #4149
closed
Register DHCP leases in DNS forwarder broken
0%
Description
On 2.1.5, the DHCP registration option in DNS Forwarding is broken. When a new machine is granted a DHCP lease, the following appears in the DHCP server's log:
Dec 26 19:40:46 dhcpd: Unable to add forward map from cali-clock.ozone.caligrafix.cl to 192.168.0.187: timed out
Dec 26 19:43:33 dhcpd: Unable to add forward map from SIP-T20P.ozone.caligrafix.cl to 192.168.0.207: timed out
I cannot see any corresponding error in the resolver's log.
This is a forum post of another user with the same problem:
https://forum.pfsense.org/index.php?topic=83418.0
Updated by Chris Buechler over 10 years ago
- Status changed from New to Rejected
not sure if that's an issue in 2.1.5 (maybe in some edge case, but there would be much more of an uproar than 2 people if it were completely broken), but it definitely works in 2.2 so nothing to look into here.
Updated by Anonymous over 10 years ago
Well, I'm sure it's an issue in 2.1.5, as I am observing it. I haven't tested 2.2 (as far as I can tell 2.1.5 is the current stable release), but I suppose that if there is an edge case in 2.1.5 that prevents this feature from working, the problem might well exist in 2.2 as well (unless that part was completely rewritten). Our DHCP and DNS configuration is really nothing fancy here.
Updated by Anonymous over 10 years ago
Now on 2.2, the bug is still present:
Feb 4 20:40:44 dhcpd: Unable to add forward map from linehead.ozone.caligrafix.cl to 192.168.0.159: timed out
(that's just one example, the log has many of these "timed out" errors).