On Tue, Mar 09, 2010 at 11:35:22PM +0200, Paul Wollner wrote:
> I have just upgraded from PowerDNS recursor 3.1.7.2 to 3.2. Unfortunately it
> appears the TTLs for records are never decremented.
>
> For the meantime I have reverted to 3.1.7.2. Is anyone else experiencing this
> problem?
Try se
Hi all,
I have just upgraded from PowerDNS recursor 3.1.7.2 to 3.2. Unfortunately it
appears the TTLs for records are never decremented.
For the meantime I have reverted to 3.1.7.2. Is anyone else experiencing this
problem?
Regards
Paul Wollner
___
On Tue, Mar 09, 2010 at 10:39:43AM -0800, Zane Thomas wrote:
> Assuming a reasonably performing backend (mysql?) what hardware will be
> required for powerdns to answer 70,000q/sec of "normal traffic" (I'm not
> sure I know how to define that!).
It depends on what number of zones and records you h
Anyone,
Assuming a reasonably performing backend (mysql?) what hardware will be
required for powerdns to answer 70,000q/sec of "normal traffic" (I'm not
sure I know how to define that!).
Tia,
Zane
___
Pdns-users mailing list
Pdns-users@mailman.powerdns
Anyone,
Assuming a reasonably performing backend (mysql?) what hardware will be
required for powerdns to answer 70,000q/sec of "normal traffic" (I'm not
sure I know how to define that!).
Tia,
Zane
___
Pdns-users mailing list
Pdns-users@mailman.powerdns
2010/3/8 Christian Kuehn
> Hi All,
>
> try to compile the new recursor and get finally this error:
>
got the same error.
Solaris10 is bundled with (/usr/sfw/bin/gcc --version) and gcc3 does not
recognize the -pthreads arguments
=> use gcc4 (blastwave for eg)
i use:
MAKE=/opt/csw/bin/gmake CX
bert hubert schrieb:
>
> For now, you could solve this problem by setting packet-cache-ttl to a lower
> number, say 20 seconds.
Thanks a lot for your quick reply, this seems to help, new records show
up much faster now.
>
> Can you also open tickets on http://wiki.powerdns.com (login with the
>
On Tue, Mar 09, 2010 at 03:06:09PM +0100, Oli Schacher wrote:
> Hi list
>
> We upgraded our resolvers to 3.2 (Centos5, 64bit)
> After the upgrade, the setting max-negative-ttl=30 does not seem to work
> anymore. New records take up several minutes until they show up in the
> cache.
> Even if we ex
Hi list
We upgraded our resolvers to 3.2 (Centos5, 64bit)
After the upgrade, the setting max-negative-ttl=30 does not seem to work
anymore. New records take up several minutes until they show up in the
cache.
Even if we explicitely perform a "rec_control wipe-cache" on those new A
record we get NX
I've now stuck a little bit in the FAQ with regards to this - hopefully any
future users will be able to find this with minimal effort and prevent any lost
time.
Chris
-Original Message-
From: pdns-users-boun...@mailman.powerdns.com
[mailto:pdns-users-boun...@mailman.powerdns.com] On B
Steve Spencer wrote:
> Just want to make sure this package is actually newer. I'm getting this
> message when I attempt to update the recursor on an CentOS5.x box:
>
> rpm -Uvh pdns-recursor-3.2-1.i386.rpm
> Preparing...###
> [100%]
>
11 matches
Mail list logo