After years they moved there cluster into VMware ...

During this NEW OES23.4 VM are created into the same tree. DNS is running at two normal hosts; DHCP is configured as clustered resource.

Meanwhile this env. is upgraded to OES 24.2.

After the last update we see that the regular updates of the zone files via DHCPd seems weak. We check the dhcpd.leases and found that sometimes the entries:

set ddns-fwd-name
set ddns-txt
set ddns-rev-name

are missing.

In the novell-named journal entry found the message:

/etc/rndc.key: file not found

The novell.named unit shows that rndc is used.

According to "">portal.microfocus.com/.../KM000009878 we run 'rndc-confgen -a' and get the file and restart the novell-named.

After that we see the message '/etc/rndc.key: permission denied' WTF??

The command 'rndc-confgen -a' create the file and set the rigths to 600. This seems as described in the rnds documention.

Ah, it looks like there is a -u named missing ...

... and next shoot ... "unsupported algorithm 'hmac-sha256' in key 'rndc-key' for use with command channel"

OK, md5 is deprecated ... and sha1 is unsupported, too. (novell-named seems to accept only md5 ...)

... sometimes I am only tried ...

Is there a detailed step-by-step documentation how to run novell-named and (clustered) novell-dhcpd incl. the dynamic zone updates?

<Rant>

As long as OT offered a product/tool this should be run and it should be supported and tested with each update! The other option is to declare EOL. In this case the customer can migrate the service (but you loose a piece of the cake again ...)

<\Rant>