Comment 4 for bug 1957086

# FYI cleanup

# Minimal Reset (e.g. when switching dnsmasq)

killall dnsmasq
rm /tmp/dnsmasq*
dnsmasq --no-daemon --log-queries --log-facility=/tmp/dnsmasq.log --conf-file=/dev/null --dhcp-leasefile=/tmp/dnsmasq.leases --bind-interfaces --interface=router_eth42 --except-interface=lo --dhcp-range=192.168.5.10,192.168.5.200 --address=/#/192.168.42.1 &
dnsmasq --no-daemon --log-queries --log-facility=/tmp/dnsmasq-vpn.log --conf-file=/dev/null --dhcp-leasefile=/dev/null --bind-interfaces --interface=testvpnrouter --except-interface=lo --address=/math.lab/10.241.3.3 --address=/cantina.company/10.241.4.4 &
dig @10.241.3.1 -t AAAA math.lab

^^ With this I could confirm that switchign the good case to dnsmasq 2.86 makes
it enter the forwarding loop. Vice versa switching the bad system to dnsmasq
2.85 makes it work (not entering the loop).

# Full cleanup
sudo killall dnsmasq
sudo rm /run/systemd/network/general.network
sudo rm /run/systemd/network/vpn.network
sudo rm /run/systemd/resolved.conf.d/test-enable-dnssec.conf
for i in testvpnrouter testvpnclient test_eth42 router_eth42; do sudo ip link dev $i down; done
for i in testvpnrouter testvpnclient test_eth42 router_eth42; do sudo ip link del dev $i down; done
sudo systemctl restart systemd-resolved
sudo systemctl restart systemd-networkd