Messages

will try that. Thank you for your help.

Thanks for your answer. To be more precise: I can see requests for PTR records in the configured upstream DNS servers for my internal network that Unbound can answer itself. If I query Unbound for an existing PTR for my internal network it answers correctly, however I can see these queries in the upstream DNS servers as well.
I think that PTR requests for local networks should not be send to the upstream servers, should they?

yes, correct

Hi,

Unbound in my installations sends PTR records of my internal LAN network to the configured query forwarding servers. I have also access to this forwarding servers and can see that the PTR records coming to them and are blocked.
This should be disabled by default but it's not.
While there are config options in Unbound to disable this behavior I was not able to set them in the config files as they are overwritten after every restart of Unbound.
I can't find an option in the GUI to disable this. DNSmasq has such option available in the GUI.
Please lmk what I can do here.

Thanks.

Update: The port chosen under control agend -> bind port must differ from the port given in the URL in Kea DHCPv4 -> HA Peers. I'm pretty sure I had the same ports there before 24.7.1. Now that the ports differ it works fine again.

------
Hi. I have an issue since upgrading to 24.7.1 where KeaDHCP is working stand-alone only.
I was running kea with HA for months now without any major problems. What I can see in the log is:

Code Select Expand

ERROR [kea-dhcp4.dhcp4.0x1ee295012000] DHCP4_INIT_FAIL failed to initialize Kea server: configuration error using file '/usr/local/etc/kea/kea-dhcp4.conf': Error initializing hooks: CmdHttpListener::run failed: unable to setup TCP acceptor for listening to the incoming HTTP requests: bind: Address already in use [system:48 at /usr/local/include/boost/asio/detail/reactive_socket_service.hpp:161:33 in function 'bind']

I tried it with another port already. Before I was using 8000 and 8001 on the secondary device. Unfortunately port change doesn't help either.

Any ideas?

Thanks.

ok then and thanks for the info. I will check out bind in OPNSense and maybe migrate.

I'm sure I had the option to set CNAMEs in Unbound in OPNSense. Although they are not visible in the web UI anymore the server answers to requests for this CNAMEs correctly.

Can you tell me if there's a config file or a database where I can do a lookup for this entries?

Nevertheless I have to use A-Records again.....

Hello community,

I've upgraded to 22.7 today. Everything's fine so far except CNAME in Unbound. They are simply gone in Web UI.
I can't see CNAME records or add new ones. However clients can resolve CNAME records created before the upgrade.
Is this a bug or intentionally?

thanks