Dhcp: Could not run unbound-control local_data

Looking at /var/log/messages I saw this (3 days ago),
has anyone seen that before ?

May 24 12:04:23 ipfire dhcp[7939]: Could not run unbound-control local_data u20s.lan 60 IN A 10.0.0.48, error code: 1: 
May 24 12:04:23 ipfire dhcp[7939]: Could not run unbound-control local_data focal.lan 60 IN A 10.0.0.39, error code: 1: 
May 24 12:04:23 ipfire dhcp[7939]: Could not run unbound-control local_data T5600.lan 60 IN A 10.0.0.26, error code: 1: 
May 24 12:04:23 ipfire dhcp[7939]: Could not run unbound-control local_data T430.lan 60 IN A 10.0.0.32, error code: 1: 
May 24 12:04:23 ipfire dhcp[7939]: Could not run unbound-control local_data android-2b7c424184b5cb86.lan 60 IN A 10.0.0.17, error code: 1: 
May 24 12:04:23 ipfire dhcp[7939]: Could not run unbound-control local_data um20.lan 60 IN A 10.0.0.23, error code: 1: 
May 24 12:04:23 ipfire dhcp[7939]: Could not run unbound-control local_data pop.lan 60 IN A 10.0.0.30, error code: 1:

3 months later, I still get those messages …
My DNS is 8.8.8.8, udp, standard
No other services are running on my firewall.

Hi Paul!

it might help the experts to add a screenshot of your DHCP page (menu Network > DHCP Server). And your Hosts page (menu Network > Edit Hosts).

my hosts

DHCP server

Wild guess based on giggling the error. Had you found this in the old forum?
https://forum.ipfire.org/viewtopic.php?t=19885

or maybe this (since PTR is enabled):

Sorry for the wild swings. It is all I’ve got…

I’ve read that link, my root.key is not empty

-rw-r--r-- 1 nobody nobody 1252 Aug 24 13:36 /var/lib/unbound/root.key

/var/ipfire/main/hosts … same as GUI

on,10.0.0.1,ipfire,lan,on
on,10.0.0.5,pve5,lan,on

Hello paul,

i can here not really help but i have about your settings a question. Maybe this leads to something good? :wink:

While setup your ipfire you already gave a host/dom name. Why you have here added again? Does anything change if you deactivate your ipfire entry here?

I added ipfire (10.0.0.1) in the hosts so that I can type ssh root@ipfire instead of ssh root@10.0.0.1

No changes if I remove that entry.

Any update on this? still today, I get:

Oct 24 16:43:41 ipfire dhcp[17760]: Could not run unbound-control local_data main.lan 60 IN A 10.0.0.47, error code: 1: 
Oct 24 16:43:41 ipfire dhcp[17760]: Could not run unbound-control local_data lake.lan 60 IN A 10.0.0.43, error code: 1: 

core 150, red/green, no rules, dns is udp/standard, 8.8.8.8

core 159, still getting those “error code: 1: b” when I restart DHCP

Dec  3 04:49:15 ipfire dhcp[18039]: Could not run unbound-control local_data xps.lan 60 IN A 10.0.0.42, error code: 1: b''
Dec  3 04:49:15 ipfire dhcp[18039]: Could not run unbound-control local_data T5600.lan 60 IN A 10.0.0.36, error code: 1: b''
Dec  3 04:49:15 ipfire dhcp[18039]: Could not run unbound-control local_data fx.lan 60 IN A 10.0.0.21, error code: 1: b''

Tried it on a VirtualBox test environment, I do not get those errors.

Does that mean my unbound data is corrupt somewhere?

Hi Paul,

I am not sure why you are encountering what you are. However I can confirm that I don’t see any messages like that in my production or vm development IPFire machines.

I tried searching on the error code number but unbound-control has an error number of 0 when everything works well and 1 when any error occurs.

All the IP’s showing a problem are from the dhcp dynamic range. The earliest ones had no additional info after the error code: 1: entry but the latest ones you show have error code: 1: b’’ but I haven’t been able to find anything when searching for that either.

Do any of those entries giving a problem appear in /etc/unbound/hosts.conf/

Do any of the hostnames for those clients having a problem have peculiar characters in their hostnames such as spaces.

So T5600.lan in the above presumably means that T5600 is the hostname for that client . Is T5600 the complete hostname or did something get cut off due to a space or unusual character.

Beyond the above I don’t have any further ideas.

I’m stumped as well …
I rebooted my ipfire, I still see those errors.
I turned OFF my ipfire, let the electrons die, then powered up. Still, same errors.
My thought is take a backup, re-install ipfire, reconfigure it, and restore from backup.

That error comes from the unbound-dhcp-leases-bridge code, line 546

ref: ipfire-2.x/unbound-dhcp-leases-bridge at master · ipfire/ipfire-2.x · GitHub

@bonnietwin regarding /etc/unbound/hosts.conf

I only have 2 static hosts, (ipfire 10.0.0.1 and pve5 10.0.0.5) but if I cat the file, line 1 is repeated as line 5, line 3 I have no idea where it came from (none of my network uses 192.168.*) so something is out of whack. Tried to flush everything in unbound, was not successful.

[root@ipfire ~]# cat /etc/unbound/hosts.conf 
# This file is automatically generated and any changes
# will be overwritten. DO NOT EDIT!

local-data: "ipfire.lan 60 IN A 10.0.0.1"
local-data: "1.0.0.10.in-addr.arpa 60 IN PTR ipfire.lan"
local-data: "1.1.168.192.in-addr.arpa 60 IN PTR ipfire.lan"
local-zone: lan transparent
local-data: "ipfire.lan 60 IN A 10.0.0.1"
local-data: "pve5.lan 60 IN A 10.0.0.5"
local-data: "5.0.0.10.in-addr.arpa 60 IN PTR pve5.lan"

ipfire.lan appears twice in the above list. Probably the first once from setup. Maybe the second one from menu Network > Edit Hosts ?

I am curious - do you have ipfire in the edit hosts page? (I do not)

If so, you may want to delete it and see if it helps.

I need to have it else the hostname ipfire would not resolve.

FYI - I created an SSH config file so shorten my ssh entries. Instead of:

ssh -p '222' root@192.168.1.1

I type

ssh ipfire

look up ssh config

That is probably a different issue. ( I am trying to remember where hostname is stored on the IPFire…)

EDIT:
Here is one in setup:
hostname_v1

EDIT2:
Here is the other:
interface_red_dhcp

What are yours set to?