If your DNS server configuration is returning multiple IP address translations for a given DNS host name and as is used for load balancing in some network environments, then it's indeterminate which translation is returned for a particular DNS query. What gets returned from the DNS server for a query is entirely up to the particular DNS server and its behavior and any local configuration customizations, including related details such as the Time To Live (TTL) setting.
Additionally, please do not use the .local TLD for local DNS; that tends to cause issues. Please use a real and registered domain. Microsoft unfortunately encouraged folks to squat in .local, and .local is now an allocated and real TLD. They've since remediated those recommendations. The .local TLD is used by and reserved to Zeroconf/Bonjour/mDNS usage. Mixing unicast DNS and multicast DNS doesn't always end well. As one of the Apple networking engineers that worked on Zeroconf/Bonjour/mDNS had commented a while back, "expect aggravation" when that usage happens.
If you're posting obfuscated details and are not really using the .local TLD here, then example.com, example.net and example.org are available for that, as are IP addresses 192.0.2.0/24 (TEST-NET-1), 198.51.100.0/24 (TEST-NET-2), and 203.0.113.0/24 (TEST-NET-3), or from one of the three private blocks. Using these names can make it easier to understand which details are intentionally obfuscated and which might be odd or might be a mistake, in particular.
