Re: making socket.getaddrinfo use cached dns

2011-07-08 Thread high bandwidth
my /etc/resolv.conf says: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by > resolvconf(8) > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN > nameserver 127.0.0.1 > search Dynex > But getaddrinfo still takes a lot of time for repeated queries. After instal

Re: making socket.getaddrinfo use cached dns

2011-07-07 Thread Nobody
On Fri, Jul 8, 2011 at 4:18 AM, high bandwidth wrote: >> I use cached dns lookups with pdnsd on my ubuntu machine to speed up >> web access as regular lookups can take 15-30 seconds. However, python's >> mechanize and urllib etc use socket.getaddrinfo, which seems not to be >> using dns cacheing

Re: making socket.getaddrinfo use cached dns

2011-07-07 Thread Chris Angelico
On Fri, Jul 8, 2011 at 4:18 AM, high bandwidth wrote: > I use cached dns lookups with pdnsd on my ubuntu machine to speed up web > access as regular lookups can take 15-30 seconds. However, python's > mechanize and urllib etc use socket.getaddrinfo, which seems not to be using > dns cacheing or ta

making socket.getaddrinfo use cached dns

2011-07-07 Thread high bandwidth
I use cached dns lookups with pdnsd on my ubuntu machine to speed up web access as regular lookups can take 15-30 seconds. However, python's mechanize and urllib etc use socket.getaddrinfo, which seems not to be using dns cacheing or taking a long time because of ipv6 lookups. In either case, I sub