Dynamic host to static host orphans DHCP DNS records

[GoogleCodeExporter]

Problem:

When changing a host from dynamic to static, the dynamically generated DNS
records still remain. This is usually noticed quickly by the user because
they are likely to use their new static host as a server of some kind and
the lookups don't resolve correctly.

Fix:

I believe the only place where this is a problem is in the DBInterface
change_registration() function. In the state of going from a dynamic to a
static host, the old dynamically generated DNS records need to be deleted. 

Additional information:

Are there other state transitions that this will happen in? Also, we should
probably find and delete currently orphaned records.

Original issue reported on code.google.com by fotinaki...@gmail.com on 27 Jan 2009 at 6:06

[GoogleCodeExporter]

This should be fixed in trunk as of r123.  When deleting a dynamic host, we now
delete dhcp dns records that have that name.

Original comment by ekoyle@gmail.com on 28 Jan 2009 at 8:04

• Changed state: Fixed

[GoogleCodeExporter]

In the del_dhcp_dns_record, do we need any permissions checking?

Original comment by fotinaki...@gmail.com on 28 Jan 2009 at 8:15