At 10:52 PM +0900 2005-03-11, Stephen J. Turnbull wrote:
I don't know about Server, but on ordinary Mac OS X I see that error fairly frequently. As far as I can tell my university's network just takes an awful long time to get the domain lookups back, and Mac OS X times out. Try again, and I almost always get immediate satisfaction.
Now that you mention it, I'm reminded that there's a bug in the MacOS X resolver. They set the retry and timeout values way, way too low, which causes a lot of errors of this sort. I don't know exactly what they screwed-up in lookupd, but this is a known major bug, and I'm afraid that there's not really anything that any normal user can do to fix it.
You can run a local caching nameserver on the machine, and this can help. But only Apple can truly fix lookupd.
-- Brad Knowles, <[EMAIL PROTECTED]>
"Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety."
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755SAGE member since 1995. See <http://www.sage.org/> for more info. ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
