Comment 2 for bug 1694156

Hi Steve,
thanks for bringing that up and debugging that much already.
In regard to this issue you kind of continued in bug 1694161.
You outlined there that the reason this hit you more than others was that you added a /etc/resolvconf/resolv.conf.d/tail to make libvirts dns resolution known in the host.
I like the suggestion you made there as a proper solution via libvirt registering "correctly" into systemd resolvd.

I wondered if I should close the bug here as a dup to the other one then.
But since this will take time to be worked on, upstreamed, and so on I wondered if you tried to add
"--dns-loop-detect" as a workaround for your setup.
It might break the DNS forwarding loops, but retain the name resolution you wanted.

Do you think that is worth a try?