named prerequisite not satisfied (YXDOMAIN)

[kriticar]

My dhcpd server correctly servers IP addresses, but when named has to refresh the zone file, it reports 'name not in use' prerequisite not satisfied (YXDOMAIN). After that, named inserts the record in the zone file, but after 12 hours, here we go again.

As network works well, why I am getting prerequisite not satisfied (YXDOMAIN) messages?

Mar 23 09:13:14 server dhcpd: DHCPREQUEST for 192.168.2.73 from 00:25:36:86:56:bc via enp1s7
Mar 23 09:13:14 server dhcpd: DHCPACK on 192.168.2.73 to 00:25:36:86:56:bc via enp1s7
Mar 23 09:13:14 server named[20383]: client 192.168.2.1#48164/key dhcp_updater: updating zone 'evident.loc/IN': update unsuccessful: B431-8656BC.evident.loc: 'name not in use' prerequisite not satisfied (YXDOMAIN)
Mar 23 09:13:14 server named[20383]: client 192.168.2.1#48164/key dhcp_updater: signer "dhcp_updater" approved
Mar 23 09:13:14 server named[20383]: client 192.168.2.1#48164/key dhcp_updater: updating zone 'evident.loc/IN': deleting rrset at 'B431-8656BC.evident.loc' A
Mar 23 09:13:14 server named[20383]: client 192.168.2.1#48164/key dhcp_updater: updating zone 'evident.loc/IN': adding an RR at 'B431-8656BC.evident.loc' A
Mar 23 09:13:14 server dhcpd: Added new forward map from B431-8656BC.evident.loc to 192.168.2.73
Mar 23 09:13:14 server named[20383]: client 192.168.2.1#48164/key dhcp_updater: signer "dhcp_updater" approved
Mar 23 09:13:14 server named[20383]: client 192.168.2.1#48164/key dhcp_updater: updating zone '2.168.192.in-addr.arpa/IN': deleting rrset at '73.2.168.192.in-addr.arpa' PTR
Mar 23 09:13:14 server named[20383]: client 192.168.2.1#48164/key dhcp_updater: updating zone '2.168.192.in-addr.arpa/IN': adding an RR at '73.2.168.192.in-addr.arpa' PTR
Mar 23 09:13:14 server dhcpd: Added reverse map from 73.2.168.192.in-addr.arpa. to B431-8656BC.evident.loc

12 hours latter...

Mar 23 21:13:17 server dhcpd: DHCPREQUEST for 192.168.2.73 from 00:25:36:86:56:bc via enp1s7
Mar 23 21:13:17 server dhcpd: DHCPACK on 192.168.2.73 to 00:25:36:86:56:bc via enp1s7
Mar 23 21:13:17 server named[20383]: client 192.168.2.1#48164/key dhcp_updater: updating zone 'evident.loc/IN': update unsuccessful: B431-8656BC.evident.loc: 'name not in use' prerequisite not satisfied (YXDOMAIN)
Mar 23 21:13:17 server named[20383]: client 192.168.2.1#48164/key dhcp_updater: signer "dhcp_updater" approved
Mar 23 21:13:17 server named[20383]: client 192.168.2.1#48164/key dhcp_updater: updating zone 'evident.loc/IN': deleting rrset at 'B431-8656BC.evident.loc' A
Mar 23 21:13:17 server named[20383]: client 192.168.2.1#48164/key dhcp_updater: updating zone 'evident.loc/IN': adding an RR at 'B431-8656BC.evident.loc' A
Mar 23 21:13:17 server dhcpd: Added new forward map from B431-8656BC.evident.loc to 192.168.2.73
Mar 23 21:13:17 server named[20383]: client 192.168.2.1#48164/key dhcp_updater: signer "dhcp_updater" approved
Mar 23 21:13:17 server named[20383]: client 192.168.2.1#48164/key dhcp_updater: updating zone '2.168.192.in-addr.arpa/IN': deleting rrset at '73.2.168.192.in-addr.arpa' PTR
Mar 23 21:13:17 server named[20383]: client 192.168.2.1#48164/key dhcp_updater: updating zone '2.168.192.in-addr.arpa/IN': adding an RR at '73.2.168.192.in-addr.arpa' PTR
Mar 23 21:13:17 server dhcpd: Added reverse map from 73.2.168.192.in-addr.arpa. to B431-8656BC.evident.loc

[aks]

I don't really see a error here. But there again:

but after 12 hours, here we go again.

What's your DHCP lease time?

[kriticar]

default-lease-time 86400;
max-lease-time 86400;

[kriticar]

Looks like it happens only with fixed IP's served by dhcpd.

[aks]

Seems like we get the YXDOMAIN error and then later, successful register. Could it be that there are two "dhcp-updater" keys used, the first one fails and the second one succeeds?