Tridion Dynamic Linking has built in proximity logic, that means that if the same component is on two pages, dynamic linking will link to the page which is 'nearest' the source page containing the link (using the algorithm described in the docs).
In the DXA (2.0) it seems that this proximity logic is not being applied when resolving links on a page returned from the Model Service. There doesn't seem to be any way to control which page links resolve to, which is a big problem if you are implementing or migrating a site with a lot of content reuse within a single publication. In any case its a big functional blind spot in the DXA framework.
There is already a Github issue for this: https://github.com/sdl/dxa-web-application-java/issues/104