Project

General

Profile

Bug #3710

Adding static DHCP leases doesn't cause BIND zones to update

Added by Dmitriy K about 3 years ago. Updated 3 months ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
Package System
Target version:
Start date:
06/12/2014
Due date:
% Done:

0%

Affected version:
All
Affected Architecture:
All

Description

Adding static DHCP leases doesn't cause BIND zones to update with "Register DHCP static mappings" on.

This one must be fixed in 2.2 for sure otherwise "If this option is set, then DHCP static mappings will be registered in DNS, so that their name can be resolved" is a pure lie because they, in fact, doesn't registered atm at all.

Sorry for my English.

Associated revisions

Revision a207d2c9
Added by Doktor Notor 4 months ago

Update BIND zones when adding static DHCP leases if needed (Bug #3710)

Revision c3fb0119
Added by Doktor Notor 4 months ago

Update BIND zones when adding static DHCP leases if needed (Bug #3710)

History

#1 Updated by Jim Pingle about 3 years ago

  • Target version deleted (2.2)
  • Affected version deleted (2.2)

#2 Updated by Chris Buechler over 2 years ago

  • Category set to BIND

#3 Updated by Rob Millner about 2 years ago

Affected by this as well on pfSense 2.2.2; BIND plugin 0.3.9.

Is there a good workaround for this issue?

The simplest one I've found is to navigate to the "Zones Settings" page and hit "Save" after adding DHCP leases; but that doesn't update the domain serial numbers.

Thanks!

#5 Updated by Kill Bill 3 months ago

Merged, please test with latest 2.4 snapshot.

#6 Updated by Jim Pingle 3 months ago

  • Project changed from pfSense Packages to pfSense
  • Category changed from BIND to Package System
  • Status changed from New to Feedback
  • Assignee set to Dmitriy K
  • Target version set to 2.4.0
  • Affected version set to All
  • Affected Architecture set to All

Also available in: Atom PDF