Activity log for bug #1686234

Date Who What changed Old value New value Message
2017-04-25 22:44:21 Mike Pontillo bug added bug
2017-04-25 22:50:05 Mike Pontillo maas: assignee Mike Pontillo (mpontillo)
2017-04-25 22:50:34 Mike Pontillo maas: milestone 2.2.1 2.2.0rc3
2017-04-26 02:30:12 Launchpad Janitor branch linked lp:~mpontillo/maas/dns-dhcp-fixes--bug-1686234
2017-04-26 04:23:15 Mike Pontillo summary [2.2] MAAS does not delete DNS records for released DHCP leases [2.2] MAAS does not correctly manage DNS for DHCP-provided hostnames
2017-04-26 13:51:21 Andres Rodriguez maas: status Triaged In Progress
2017-04-26 22:31:10 Mike Pontillo description When a DHCP lease is created, MAAS uses the hostname provided by the DHCP client to create a DNS record. This has two issues: (1) Hostnames with invalid characters are allowed. For example, I saw a hostname like "Nintendo 3DS.maas" on my home MAAS. (2) When the DHCP lease is released, the DNS record is not removed; it remains in the database with no IP addresses associated with it. When a DHCP lease is created, MAAS uses the hostname provided by the DHCP client to create a DNS record. This has several issues: (1) Hostnames with invalid characters are allowed. For example, I saw a hostname like "Nintendo 3DS.maas" on my home MAAS. (2) When the DHCP lease is released, the DNS record is not removed; it remains in the database with no IP addresses associated with it. (3) When a DHCP lease is acquired, it can add a DNS record that clashes with the hostname of an existing node. (4) A dynamic DHCP request can incorrectly affect an existing preconfigured static DNS entry.
2017-04-27 15:43:29 Andres Rodriguez maas: milestone 2.2.0rc3 2.2.0rc4
2017-04-27 16:13:05 Mike Pontillo maas: importance Medium High
2017-05-05 13:56:40 MAAS Lander maas: status In Progress Fix Committed
2017-05-12 20:21:03 Andres Rodriguez maas: status Fix Committed Fix Released