Bert,
Follow the recursor.conf:
# Drop uid
setuid=nobody
# Drop gid
setgid=nobody
# Don't log queries
quiet=on
# Local IP address to bind to
local-address=10.1.1.140
# Local port to bind to
local-port=53
# Change root for safety
chroot=/var/lib/powerdns
# Bloqueia malware
auth-zones=malwar
Hi all,
I recently installed pdns and pdns-recursor to test it before deploy it.
However I have a little problem : when I used option "fork" in
pdns-recursor config, I can't use rec_control to have some statistic. I
obtain this error :
Fatal: Unable to connect to remote
'/var/run/pdns_recursor
Thanks for the link. We also looked at NSD which is another good one. unbound
appears to be threaded? That would offer the performance gains. Especially on
the quad-core CPU's we use. However my current configuration launches multiple
pdns instances in the forked mode each on a seperate IP using
On Tue, Aug 05, 2008 at 10:29:14AM +0200, Leen Besselink wrote:
> On Tue, Aug 05, 2008 at 12:30:25AM -0700, Brad Dameron wrote:
> > And you will see your response times drop from 1-2 seconds to milliseconds.
> > I did a lot of testing of this and pdns-recursor is definitely the best out
> > there
On Tue, Aug 05, 2008 at 10:29:14AM +0200, Leen Besselink wrote:
> I can't find the graph. The graph I've seen shows PowerDNS and bind pretty
> close together. Which I found a bit strange.
That was BIND before they did source port randomisation, which we've been
doing since 2006.
Bert
--
On Tue, Aug 05, 2008 at 12:30:25AM -0700, Brad Dameron wrote:
> And you will see your response times drop from 1-2 seconds to milliseconds. I
> did a lot of testing of this and pdns-recursor is definitely the best out
> there.
>
> Brad
>
Hi Brad,
Did you also test Unbound ( www.unbound.net
And you will see your response times drop from 1-2 seconds to milliseconds. I
did a lot of testing of this and pdns-recursor is definitely the best out there.
Brad
From: [EMAIL PROTECTED] on behalf of Adam Cassar
Sent: Mon 8/4/2008 6:44 PM
To: pdns-users@mailm
