Comment 16 for bug 1682499

This helped me only partially - I still have issues with DNS lookup.

It seems that the systemd-resolved is broken from the very idea.

After solving DNSSEC problem, I see now a switching problem - if one DNS does not respond, resolved switches to another one, which may be a local DNS not serving all the information, however it responds RELIABLY with .... "REFUSED" for majority of queries! Thus, resolved is stuck with this "reliable" DNS, refusing almost all queries until reboot (or networking reload).

There are so many bugs filled about resolved that somebody should gather them in one place and do something.

Moreover, tracing problems is not easy - they are intermittent, depending on current server load. For some people in fixed setup bug may be nonexistent; when travelling across well-configured, simple and non-overloaded networks everything is OK. Then, at some hour, some connection - I start having to reload network every time I start reading mail.....

For now many people are switching to alternative resolver - e.g. "unbound"; what is going on with resolved looks like sabotage.....