[Bug 1899146] Re: systemd-resolve has no --verbose or --debug flag

[Dimitri John Ledkov]

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.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1899146

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

Status in systemd package in Ubuntu:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1899146/+subscriptions