Dynamic analysis tools provide runtime information of the state of the executing software. They can be used to pinpoint a number of
problems that are hard to find in static analysis and dynamic
testing.

So it is clear that this is correctly saying DA is not
dynamic testing (Wikipedia does not agree but that is not trusted
source).

Another source: Guide to Advanced Software Testing:

Dynamic analysis cannot be done without tool support.... provides information as a by-product of dynamic testing (...) Dynamic testing can be
used when the test object is executable. We can also use dynamic analysis, especially during component
testing.

To perform dynamic analysis (memory leaks...) you have to execute the program, so I should try to provide a clear description when defining "dynamic testing" as a different aspect than "dynamic analysis" (and not just in a way of "exercising the program").

Usually, the test cases executions (from unit testing to regression system/function test) are used in order to produce the dynamic analysis reports. Not necessary, but let's say a "real world" relationship between them.

Maybe you should try to find a definition that focus on the objetives (results). "Static/dynamic code analysis" are mainly focused on the code violations/pitfalls no matter what functionality is implemented. "Dynamic testing" take care of how functionality (requirements) are implemented.