F23 does not renew dhcp leases correctly and corrupts DDNS

[Tim]

Allegedly, on or about 25 January 2016, Greg Woods sent:
> (I can't remember how to get a dump of the zone, but I remember doing
> it in the past.

Simply stopping the nameserver ought to cause it to reconcile its
records on file.  That's what I do when I've struck a DNS/DHCP foul-up.
Stop DHCP server, Stop BIND, edit records, increment the serial number,
restart BIND, restart DHCP server.

That sort of thing tends to happen when you're experimenting, and
haven't invented a new IP outside of the DHCP pool.

e.g. If your LAN uses 192.168.0.0, then set aside a range to be dynamic,
such as 192.168.0.1 to 192.168.0.100, and configure your DHCP server to
only dole out those addresses to dynamic clients.  For static addresses,
whether individually set on the client equipment, or handed out as fixed
DHCP addresses, use IPs outside of that range.

Other things that confuse DHCP/DNS server combinations are dual-boot
PCs, where on one OS the DHCP client sends out prefix codes that the
other does not, and the DHCP server looks at those codes as well as MAC
addresses, and doesn't give the same PC the same address for each OS.
Which is logical enough, except that it doesn't properly reset the one
it'd previously doled out to the same PC.  It gets truly messy if the PC
uses the same hostname on both OSs.  I've seen reverse IP records stay
stale, and forward ones updated.


-- 
[tim at localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted, there is
no point trying to privately email me, I only get to see the messages
posted to the mailing list.

I'd just like to say that vinyl record crackles and pops are far less
annoying than digigigigital mu-u-u-u-usic hiccicicicups and
yooo-----------------u tu-----be ....... pauses.