Windows boxes will do this sorting by default, subject to a registry
setting, see http://technet.microsoft.com/en-us/library/cc961422.aspx
Other client OSes may or may not sort automatically, but if you want to
force a particular sorting on the server side and you have no
intermediate resolvers (including the clients' own name-resolution
caches, if enabled) which might re-order the responses, check out BIND's
"sortlist" directive.
Another thing to consider is: what if the client connects to the *wrong*
IP address? Is this just sub-optimal from a performance standpoint, or
is it a fatal error? If the client can't tolerate occasional "wrong"
connections, then you need to give discretely *different* answers to the
relevant query/queries, in which case you need to look at implementing
"view"s. But this is a heavyweight solution since it means maintaining
different versions of zones in parallel.
- Kevin
On 8/20/2010 5:18 AM, Julian Pilfold-Bagwell wrote:
Hi All,
I've searched Google for a direct answer to this question but no joy
so I'd really appreciate some help.
I have a multi-subnetted network and servers that have a presence on
each subnet, e.g. 4 NICs on in 192.168.0.0, 192.168.1.0, 2.0, 3.0 etc.
In the reverse tables I have can set up allow query statements to
control access but what happens on the forward lookups? I suspect that
the client will use the result that matches its own subnet but just
want to make sure before going on.
Thanks,
Jools
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
