I've been trying to use unbound with poor results. Currently it resolves
very very slowly. About 4 times longer then the default dns forwarder.
Once the site is found and loaded however browsing the site is
incredibly fast. Curious what might be the cause of the slow down on
initial lookup and
On 15/2/14 6:22 pm, Brian Caouette wrote:
I've been trying to use unbound with poor results. Currently it resolves
very very slowly. About 4 times longer then the default dns forwarder.
Once the site is found and loaded however browsing the site is
incredibly fast. Curious what might be the
CACHING
On 2/15/2014 1:29 PM, Chris Bagnall wrote:
On 15/2/14 6:22 pm, Brian Caouette wrote:
I've been trying to use unbound with poor results. Currently it resolves
very very slowly. About 4 times longer then the default dns forwarder.
Once the site is found and loaded however browsing the
On 02/15/2014 01:33 PM, Brian Caouette wrote:
CACHING
dnsmasq caches quite nicely.
On 2/15/2014 1:29 PM, Chris Bagnall wrote:
On 15/2/14 6:22 pm, Brian Caouette wrote:
I've been trying to use unbound with poor results. Currently it resolves
very very slowly. About 4 times longer then the
On 14-02-15 12:22 PM, Brian Caouette wrote:
I've been trying to use unbound with poor results. Currently it
resolves very very slowly. About 4 times longer then the default dns
forwarder. Once the site is found and loaded however browsing the site
is incredibly fast. Curious what might be the
Yeah, thanks. I looked around the developer site for a code overview but
didn't see much.
Where do you think the crux of the matter lies, in racoon, setkey, or the
way freebsd is handling it?
How do other firewalls on a linux platform work around this? A recompile
of ipsec tools, or deeper?
