I'm assuming the host command uses /etc/resolv.conf (rather than
the OS X resolver), which is why it would fail, but applications
like Safari would still work....
I took a quick look at the BIND source code and your assumption
appears to be correct.
On Sep 18, 2005, at 18:09 , Matthew Bogosian wrote:
After entering these commands, I can see the new resolver entry in
the output of 'scutil --dns', but domain.dom *also* gets added to
the default resolver:
What gives? Any help would be very much appreciated (incidentally,
I'm running 10.4).
We've attempted to make life a bit better for those VPN
configurations which do not become the "primary" service. The
question is how to resolve a non-fully qualified domain name. In
your example, with the VPN up, should we attempt to resolve "foo" as
only "foo.myisp.net" or as "foo.domain.dom" and then
"foo.myisp.net"? The feedback we received leaned toward the latter
with the reasoning being that the VPN is providing access to
"domain.dom" and that the VPN domain should have some preferential
treatment.
