On Wed, Oct 06, 2010 at 09:23:10AM -0700, Mark Hamilton wrote:
I don't know if this issue has already been
discussed but I didn't see
it after a quick search. I installed perdition 1.18 and set it up.
Everything worked fantastic including ssl etc... Then I started seeing
some errors like in the subject line above. After turning on debugging
I saw a mention of a temporary failure in dns before the connection
failed. I tested it myself by putting my ipad in an ip block that did
not have a dns server resolving the reverse lookup. It failed. I added
the block to a dns server where it was expected and it worked fine.
Since I don't have access to everyone's reverse ip I tried adding one
client to the hosts file on the server running perdition and it seemed
to fix the issue as well. I have an older version, 1.17, that does not
seem to have a problem with ips that do not have a proper dns server set
up. Is there anyway to stop this from happening?
Hi Mark,
that is rather curious. I would be interested to see some more of the log
messages surrounding the error, particularly with the debug configuration
option enabled. And to know if the same problem occurs in 1.19-rc4.
Although I'm not having much luck reproducing this problem I suspect that
the no_lookup configuration option can be used as a work-around.