Steve Duff said:
Herb is right.
However if you have multiple host records for the same
name with differnet IPs, and have subnet mask ordering
enabled (the default), DNS will attempt to order the IPs
in a reply so that the "closest" (classful network) to the
requester's IP appears first.
Whether this helps you depends on what you are
trying to do.
Whoo, had to think about that for a bit, but then realized
that while you are technically correct, this would seldom
hold up in real networks -- and probably not reliably if
it seemed to work.
There will be no preference for external name resolution
IF the web site has a random Internet or a private address.
(Random includes a "dedicated rental server" somewhere
else on the Internet or even the IP of the DNS server).
There will be no preference if the internal machines are
in a different range than the DMZ (e.g., the DMZ uses
172.16.x.y and the internal uses 10.x.y.z)
And any machine with but one address will be show
to all clients the same (such as an internal server which
shouldn't even appear externally resolvable.)
Don't do it.
BIND wins here.
"Views" (using ACLs) rule for this sort of thing, and I
wish it weren't so.
BTW, I actually use a BIND (free) server on my gateway
now, and MS internally for everything else due mostly to
this behavior (and being able to preload the cache with
"dead end" resolution for known "bad places.")