-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
As Carlos mentioned. The dnsmasq localise-queries flag might work for
you, if the servers are on the same subnets as the clients.
Apart from that, then the behaviour you're seeing is called
round-robin DNS and it's considered to be the polite way fo
Olivier Mauras (oliv...@core-hosting.net) wrote on Fri, Aug 21, 2015 at
11:25:35AM BRT:
> I know that the choice of IP to use is up to the client, but if
> the client is configured to use the first one in the list, the answer
> through dnsmasq won't give the "expected" result as configured on the
On 2015-08-21 15:36, Carlos Carvalho wrote:
> The choice of which
IP to use is up to the client, not the dns
> server. The default
algorithm is defined by RFC 6724.
>
> The only special feature related
to this that dnsmasq has is localise-queries.
> You didn't give the
details for us to know
The choice of which IP to use is up to the client, not the dns
server. The default algorithm is defined by RFC 6724.
The only special feature related to this that dnsmasq has is localise-queries.
You didn't give the details for us to know if it's applicable.
__
Il 20/08/2015 15:49, Olivier Mauras ha scritto:
Hello,
I use dnsmasq in front of a couple of Microsoft DNS servers. For some
reason, the Microsoft DNS service has been configured to reply in order
depending of the client subnet, always returning the nearest servers for
some DNS entries.
Sadly wh
Hello,
I use dnsmasq in front of a couple of Microsoft DNS servers.
For some reason, the Microsoft DNS service has been configured to reply
in order depending of the client subnet, always returning the nearest
servers for some DNS entries.
Sadly when asking these entries to
dnsmasq, the answere
