Opened 2 years ago

Last modified 2 years ago

#5370 new enhancement

DDNS inconsistencies due to hostname generation

Reported by: marcosgildavid Owned by:
Priority: medium Milestone: Kea1.x
Component: ddns Version: git
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DHCP Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

Kea should use MAC address to generate the hostname for clients.

Imagine I turn on a server (Server A) and it gets a IP/hostname combination of:
192.168.0.1/host-192-168-0-1.example.com

If I keep it turned off until the IP is recycled and the DNS entry removed, that IP will be assigned to a different server (which is the expected behavior).
New server (Server B) gets the same combination of IP/hostname:
192.168.0.1/host-192-168-0-1.example.com

When I turn Server A back on, it will send its hostname to Kea and get a new IP (let’s say 192.168.0.3)
However, Kea will remove the current DNS entry for Server B (host-192-168-0-1.example.com) and replace It with
192.168.0.3/ host-192-168-0-1.example.com creating obvious problems for whoever is relying in the DNS hostname.

I would expect/prefer the MAC address to be used to generate the hostname, is there any way to do this?

Subtickets

Change History (3)

comment:2 Changed 2 years ago by tmark

  • Type changed from defect to enhancement

comment:3 Changed 2 years ago by tomek

  • Component changed from Unclassified to ddns
  • Milestone changed from Kea-proposed to Kea1.x

Hi,
First of all, thanks for submitting this feature request. Yes, it does look reasonable. I think there are many ways how the hostname could be generated. We have implemented one and you prefer another. There surely may be other ways.

In my opinion the best way would be to provide an ability to specify an expression that the user would define and then Kea would use it as a template.

We did discuss this matter on our weekly Kea call today (2017-10-05) and decided it's a nice feature and we would like to have it implemented one day. Sadly, we can't squeeze it in upcoming 1.3 final for two reasons. First, past beta we tend to accept only bugfixes and this is clearly a new feature. The second reason is simply lack of manpower. We recently received a number of new requests from a customer and we need to focus on those first.

In the next release - 1.4 - we want to focus on high availability and multi-core support. Both are rather complex problems, so sadly we can't accept DDNS related feature requests.

Nevertheless, we'd like this feature to be implemented one day, so we decided to move it to 1.x. If you're disappointed with this, please contact me and we'll discuss.

Note: See TracTickets for help on using tickets.