Looks like I figured it out.
OSX's internal name resolution API calls (gethostbyname?) apparently
doesn't honor /etc/resolv.conf, but the 'host' command does.
Also, OSX doesn't like it if you've only configured 127.0.0.1 as your
only nameserver, even if you have a perfectly good local named running
on loopback. No idea why, using dig against localhost worked just
fine.
Long story short, going into System Preferences -> Networking -> Advanced -> DNS
and adding additional dns servers after 127.0.0.1 seems to have solved
the problem.
--
Aaron Turner
http://synfin.net/
http://tcpreplay.synfin.net/ - Pcap editing and replay tools for Unix & Windows
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety.
-- Benjamin Franklin
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|