Messages

1

High availability / Re: 24.7 HA with KEA DHCP

« on: August 14, 2024, 06:03:02 pm »

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]

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.

2

22.7 Legacy Series / Re: Unbound DNS CNAMEs are gone

« on: August 05, 2022, 09:24:28 am »

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

3

22.7 Legacy Series / Re: Unbound DNS CNAMEs are gone

« on: August 04, 2022, 08:13:52 pm »

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…..

4

22.7 Legacy Series / Unbound DNS CNAMEs are gone

« on: August 04, 2022, 03:56:45 pm »

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