> An unfinished dbus call should only happen when the server fails > internally and aborts the connection. If there's an error or timeout in > the query resolution, it should still terminate the connection with > some response. > > Please enable debug logs with 'resolvectl log-level debug' and do the > reproducer and show the logs. I think it'd be better to do this in BZ > though, it seems too complex for the mailing list. > Please also include rpm versions and 'resolvectl status' output. $ resolvectl query example.com example.com: 93.184.216.34 2606:2800:220:1:248:1893:25c8:1946 -- Information acquired via protocol DNS in 1.6ms. -- Data is authenticated: no $ resolvectl query com.example com.example: resolve call failed: All attempts to contact name servers or networks failed That's totally on me, I read the resolved.conf(5) manual but didn't pay attention to the systemd-resolved.service(8) manual in the SEE ALSO section: that would have led me to resolvectl. Thanks for the pointer, I'll do some reading, probably figure what I mis-configured and otherwise file a BZ. Cheers _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
