You also have to account for how your individual programming language handles DNS lookups - i.e. does it do its own caching? Round robin can quickly breaks down when using DNS.
This is the reason why kubernetes uses proxying rather than DNS for load balancing. The number of pitfalls with using DNS for loadbalancing are just too large.
My intention was to send the same message. That's why I put Docker DNS as "potentially useful but still in its infancy".