About one booting in 20 (I reboot daily just before the daily clone to ensure cloning a bootable system), my system gets into a weird state. I can do direct DNS lookup (host red.stonehenge.com succeeds), but not "normal" lookup usage (ping red.stonehenge.com fails with host not found). If I use the literal IP address in the ping command, it works, so it's not the ping command itself. The only way I've found to correct this condition is to reboot my system. Changing "network location" or DNS servers isn't enough. And it's system-wide... I can't visit a site in Safari... I can't ssh to a named host, etc.
I know there's some sort of layer for "normal" lookup (directory services?) that sits between most apps and DNS. Is there some place I can look to see what errors it might be spewing, or to see if it has come up with the wrong setting, or better yet, a way to "restart directory services" without going through a full reboot? -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <[email protected]> <URL:http://www.stonehenge.com/merlyn/> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.posterous.com/ for Smalltalk discussion _______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
