[Twisted-Python] New TLS Code *Could* Cause Problems

Reza Lotun rlotun at gmail.com
Tue Jul 19 06:36:39 MDT 2011

On Tue, Jul 19, 2011 at 12:16 PM, Phil Mayers <p.mayers at imperial.ac.uk>wrote:

> Well, TBH if you're not running a local caching nameserver, I am failing
> to see how anything works!

Hmm, it turns out I may have been a bit too hasty in blaming the newtls code
perhaps. We're running tests on resolver calls on the old setup vs. the new
one, and the behaviour is the same on on our pre-trunk (standard) config. We
may have just hit some threshold where it has suddenly started to matter, I

Anyway, I suppose the real lesson is the non-caching of gethostbyname calls.
Not being a DNS guru, I had no idea calls weren't cached locally. Let that
be a lesson, I guess.


Reza Lotun
mobile: +44 (0)7521 310 763
email:  rlotun at gmail.com
work:   rlotun at twitter.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/twisted-python/attachments/20110719/e8593d14/attachment.html>

More information about the Twisted-Python mailing list