23.1.7_3 Unbound starting error due to special characters in hostname

[AdiH]

Unbound can´t start unbound service due to special characters in the hostname of an IoT-device:

# unbound-checkconf /var/unbound/unbound.conf
[1683303806] unbound-checkconf[82621:0] error: error parsing local-data at 34 '56;2;1;1.53.local IN A 10.10.10.74': Syntax error, could not parse the RR's TTL
[1683303806] unbound-checkconf[82621:0] error: Bad local-data RR 56;2;1;1.53.local IN A 10.10.10.74
[1683303806] unbound-checkconf[82621:0] fatal error: failed local-zone, local-data configuration

If i delete the two lines in "/var/unbound/dhcpleases.conf" everything is ok again.

My problem is, that i can´t change the hostname because it´s an IoT-device, a Brother Sewing machine of my wife ;)

Bye

[AdiH]

Any news on that?
With OPNsense 23.1.9 the error is still existent.

I understand that the root cause for this error is the wrong hostname coming from the brother sewing machine but i cant edit the hostname manually.
But i think its not normal that the whole unbound service crashes and can´t be restarted without editing the dnsleases.conf manually.
Maybe its a way to submit this error to the package maintainer of unbound directly? Can anybody tell me how i can do that?

The error is for me very annyoing because i have to forbid my wife to use her sewing machine because she will crash our whole network otherwise ;)

Bye, Adrian

[Patrick M. Hausen]

Disable dynamic DNS updates? But her sewing machine in a separate network and just disable there?

[AdiH]

Disable dynamic DNS updates? But her sewing machine in a separate network and just disable there?

Thanks for your suggestions. Where can i disable dynamic DNS?
The separation of the machine in an other network is also a good idea, thanks.

But coming back to the actual problem, I don't think it's nice that the commissioning of a single network device can paralyze the entire network. The unbound maintainer should definitely know that...

[Patrick M. Hausen]

I'd blame the somewhat crude mechanism by which OPNsense performs DNS updates from DHCP. Ideally it should use RFC 2136. Instead it generates config files and reloads unbound. If these are syntactically incorrect, well ...

Another idea: give that sewing machine a static IP address in the DHCP settings and do set a hostname. Possibly when it receives one from DHCP it will honour that. Plus, IIRC will register that name with Unbound no matter what the device does.

[EdwinKM]

filing a bug report will increase the change to be addressed.

[AdiH]

Another idea: give that sewing machine a static IP address in the DHCP settings and do set a hostname. Possibly when it receives one from DHCP it will honour that. Plus, IIRC will register that name with Unbound no matter what the device does.

Good idea, the device gets an new hostname but the issue still persists.

[AdiH]

filing a bug report will increase the change to be addressed.

Thanks, i filled a bug report on github right now.

[Patrick M. Hausen]

filing a bug report will increase the change to be addressed.

Thanks, i filled a bug report on github right now.

You probably need to delete the dynamic lease from dhcpd.

[AdiH]

You probably need to delete the dynamic lease from dhcpd.

Thanks, didn´t help either