systemd-resolve has no --verbose or --debug flag

[Olivier Godart]

I understand that systemd-resolve is the tool to test queries through systemd-resolved.

When investigation resolution issues (if it resolves fine with dig @server domain.to.test but not with systemd-resolved), you can use systemd-resolve --status to view the active configuration with the link related parameters, OR use systemd-resolve domain.to.test to test the resolution (but you have no details, just either a result, or a simple "not found").

It would really help a lot to have either a --verbose or a --debug flag, to see which server is queried, why, which domains are actually sent in the query (based on the search domains), was the cache used (something like the dig output would already be better).

Thanks!

Ubuntu version: Ubuntu 18.04.5 LTS
Systemd version: 237-3ubuntu10.42

[Sebastien Bacher (seb128)]

Thank you for your bug report, that's the sort of requests that would probably make more sense to be reported directly upstream

https://github.com/systemd/systemd/issues

[Olivier Godart (olivier-godart-gmail)]

Hi Sebastien, I just opened this feature request on the upstream: https://github.com/systemd/systemd/issues/17330

[Dimitri John Ledkov (xnox)]

You can start systemd-resolved (the daemon side of it) with Environment=SYSTEMD_LOG_LEVEL=debug.

Then you will have more data of what is being asked; where the requests go; what is returned, etc.

Do not forget to drop caches between requests!

But I do agree cli option would be nice.

[Dan Streetman (ddstreet)]

this is a request that must be taken upstream, not to ubuntu