Created attachment 1728 [details] Details for reproduction On core203 in testing: The new knot-resolver seems to not support multiple IP entries for a single host.domain entry. Adding multiple entries with different IPs for a single host.domain to Network > Hosts used to work with unbound. According to the upstream bug report, adding multiple entries with the same name should be fixed and work: https://gitlab.nic.cz/knot/knot-resolver/-/work_items/808 This also affects modifying the configuration file /etc/knot-resolver/config.yaml with keys in `/local-data/addresses` and loading a hosts file with `/local-data/addresses-files`. However, adding these as raw records via `/local-data/records` works.
Hello Bernd, thanks for raising this. I don't know what we can do about this though. I think using the hints module makes most sense as it is designed to implement this functionality. Returning multiple addresses for the same host is something I didn't test personally and I don't consider it good design, but the UI allows to save them, so we should make them work. I would recommend you to file a bug upstream as it simply seems to be a regression that has been introduced after the code that you linked to has been merged.
I've escalated the issue to the upstream maintainers: https://gitlab.nic.cz/knot/knot-resolver/-/work_items/954 My use-case is to have DNS-level load balancing for some internal services I run. With the current unbound implementation I did forgo the GUI config and added them as raw records via `/etc/unbound/local.d/vhosts.conf`.
Thanks Bernd. I have added a link to this report as well for reference.
Hello Bernd, I have back ported the patch from upstream so that this should also work in IPFire: > https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=ca152073b10bbeb3bda12dc27a94fcfb5692e650 This will however be in Core Update 204.
Thanks, that's awesome! :)
Okay I changed my mind and moved 6.4.0 into Core Update 203, so it will contain a fix for this, too.
Core Update 203 has been released: > https://www.ipfire.org/blog/ipfire-2-29-core-update-203-released