Today I learned that one can simply cache-bust a specific record in systemd-resolved by using resolvectl query --cache=false example.com.

I came across this while waiting for a DNS record to become available locally, after I already tried querying it earlier resulting in the negative result being cached. While dig was only able to query the cached negative result from systemd-resolved, its own tool resolvectl has much more integrated features for this use-case. I can recommend to take a look at resolvectl query --help.