> It looks like resolved tries to resolve the name on two scopes (global and > one specific to some interface). This will happen if the name lookup priority > is the same for both the two scopes.
Interesting, I'll search the docs. I don't recall seeing anything about priority and that's definitely something I would want to tweak. > Maybe you're hitting https://github.com/systemd/systemd/issues/17040? > One of patches being prepared is > https://github.com/systemd/systemd/pull/17535/commits/1e5eb07b34bf3ee5420ed6e290ad524f8e26eebf. I'll subscribe to this issue, it definitely looks like the main problem I'm running into. > There'll be quite a number of patches for resolved in the upcoming systemd-248 > release. It'd probably make sense to wait and test if the issue is still > reproducible with 248-rc1. I had found https://github.com/systemd/systemd/pull/17535 but didn't find anything conclusive regarding my case. Maybe I should wait until the RC1 is available to reassess the situation? Would this RC1 land in updates-testing for f33? Thanks a lot _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]
