How to solve the problem with DNS?

Question

Domain Name System

Hello!
Ran into a little problem, and at the moment a little confused. The essence of the problem is as follows:
There is a DNS server with two interfaces: 10.0.0.0 and 192.168.0.0.
And two networks in which, respectively, there are computers 10.0.0.0 and 192.168.0.0.
For some A records, respectively, there are two IPs from the 10th and 192nd networks.
The netmask ordering option is enabled on the DNS server, that is, the DNS server looks from which network the request came from, and issues a list of A records in the correct order, that is, if the request came from network 192, then the first record is 192. If from network 10, then the first record 10.
Example:
> it
DNS: it.domain.local
Address: 192.168.0.241
DNS: it.domain.local
Addresses: 192.168.0.45
10.0.0.45
But! In 192 networks, for some reason, computers choose the first 10th IP shnik when pinging.
Moreover, balls and network applications work if you request a web service that is running on these servers, there is a delay of 30 seconds, then the site opens. If you register in the hosts - it opens instantly.
I tried to clean the DNS cache, even more, I turned off the DNS service altogether (that is, without the cache).
I want to understand - why is this garbage happening? The balls open, but pings and calling by name to the web service slows down .... I really don’t even understand where to dig ..
Which service selects the required IP address from the list given by DNS when pinging?
PS I tried to remove the record of the 10th network from DNS - it works fine. I add the 10th address - the client computer selects it ((
It was revealed by the method of scientific poke - for some reason the client chooses the 10th IP, although he himself is in the 192nd subnet, and DNS issues the 192nd IP first. What's wrong here...

Answer 1

Если DNS - bind и управляется вручную, то можно использовать в конфигах
view "net1"
{
match-clients { our_net1; };
...}
view "net2"
{
match-clients { our_net1; };
...}

Answer 2

А зачем вообще отдавать недоступный IP в ответе? Избавьтесь от него и все заработает без вот этих плясок с бубном.

Answer 3

Enable cross-subnet routing and assign one DNS entry to each host.

Answer 4

I remind you that for all machines on the network, you need to register some reasonable PTR records in DNS.