My router was affected by the same issue, I had to set the dnsmasq port again.
Given that the dnsmasq port is part of the user’s configuration, why did the update change it?
Could we have a statement from the Turris devs on this please?
Is setting dhcp.@dnsmasq[0].port=‘53’ not the correct way to prefer dnsmasq over knotdns?