Dear PowerDNS community,
PowerDNS Recursor 3.3 Release Candidate 3 is now available! It is in wide
production use already, but we'd like everyone to take a good look at it
before we release it as 3.3-final. If nothing crops up, RC3 will be the
exact same as the 3.3 release.
RC1 had some compilat
From: pdns-users-boun...@mailman.powerdns.com [mailto:pdns-users-
> > boun...@mailman.powerdns.com] On Behalf Of Detlef Peeters
> > Sent: Monday, September 20, 2010 2:46 AM
> > To: bert hubert
> > Cc: Pdns-users@mailman.powerdns.com
> > Subject: Re: [Pdns-users] pdns-
Odd - can you paste some 'stats:' lines from the log files?
stats: 4331362754 questions, 1003788 cache entries, 100987 negative entries,
27% cache hits
stats: throttle map: 2752, ns speeds: 76672
stats: outpacket/query ratio 3205%, 2% throttled, 0 no-delegation drops
stats: 263614 outgoing
Hi Thomas,
Try disable-packetcache, this will allow the shuffling logic to act.
The shuffling within the PowerDNS Recursor is random, and not deterministic,
though.
Good luck!
On Mon, Sep 20, 2010 at 07:51:01AM +0200, Thomas Mieslinger wrote:
> Hi,
>
> we've set up some large Round Robin Recor
On Mon, Sep 20, 2010 at 07:32:51AM +0200, Thomas Mieslinger wrote:
> we're using pdns recursor for out company internal name resolution.
> We have some strange setups to support that can't easily be removed.
>
> In some of our offical Zones are CNAMEs. The A records to these
> Names are in our int
Found it & solved in http://wiki.powerdns.com/trac/changeset/1716
This issue is harmless, but it is good to have it solved for the 'real'
release.
Thanks for the vigilance!
Bert
On Wed, Sep 15, 2010 at 01:39:11PM +0200, bert hubert wrote:
> On Wed, Sep 15, 2010 at
ecursor[1290]: zvngjzei.net.RT-G32.: our root
> > expired, repriming from hints and retrying
> >
> > Process was started _exactly_ a day before the messages appeared:
> >
> > Sep 11 23:17:15 nsc pdns_recursor[1290]: Done priming cache with root hints
> >
&g
On Wed, Sep 15, 2010 at 01:37:30PM +0200, Detlef Peeters wrote:
> pdns_recursor[32068]: objects-test.deviantart.com.edgesuite.net.:
> our root expired, repriming from hints and retrying
> pdns_recursor[32068]: s.de.net.: our root expired, repriming from
> hints and retrying
Hi Detlef,
Can you lis
Dear PowerDNS community,
PowerDNS Recursor 3.3 Release Candidate 2 is now available! It is in wide
production use already, but we'd like everyone to take a good look at it
before we release it as 3.3-final. If nothing crops up, RC2 will be the
exact same as the 3.3 release.
RC1 had some compilat
On Sat, Sep 11, 2010 at 06:43:08PM +0700, Dmitriy Lyfar wrote:
> Hi,
>
> I'm using pdns with my own backend. Previous version I've used was 2.9.21
> (from centos repo) and my backend works fine. But we decided to
> move to last version (pdns-static, 2.9.22, x86_64) and it can't even run
> with my
Dear PowerDNS community,
PowerDNS Recursor 3.3 Release Candidate 1 is now available! It is in wide
production use already, but we'd like everyone to take a good look at it
before we release it as 3.3-final. If nothing crops up, RC1 will be the
exact same as the 3.3 release.
Tar, RPM & Deb for 32
On Fri, Sep 10, 2010 at 10:20:07AM +0200, Christian Kuehn wrote:
> Hi,
>
> today I installed the Recursor 3.2 in a new Solaris 10 x86 and the
> process crashed immediately:
Hi Christian,
Sadly this is well known - see
http://mailman.powerdns.com/pipermail/pdns-users/2010-August/006956.html
Pow
e packages that will be binary identical to the real 3.3
> once you 'bless' them as having solved your issue. This would save you an
> upgrade.
>
> Would this work for you?
>
> Bert.
>
> Sent from my phone.
>
> - Reply message -
> From: "Simon
On Thu, Sep 09, 2010 at 12:10:53AM +0300, Nikolaos Milas wrote:
> Indeed, I have confirmed that pdns does not send a complete set of
> records during AXFR, by executing:
>
># dig example.com AXFR @dns.example.com
>
> where dns.example.com is the pdns/ldap server. The output is exactly
> the
On Sun, Aug 29, 2010 at 09:17:01PM +, Brad Dameron wrote:
> > The release process for 3.3 can now start - only 1 feature request left
> > to
> > finish.
>
> Good to hear Bert. I'll run it through the ringer on Monday and see if we can
> reproduce the problem. Cross fingers that it is fixed.
On Wed, Sep 08, 2010 at 08:44:01PM +0300, George wrote:
> Here are the outputs:
> [r...@webprod02 ~]# grep local-address /etc/pdns/pdns.conf
> # local-address Local IP addresses to which we bind
> local-address=0.0.0.0
(...)
> pdns[6269]: It is advised to bind to explicit addresses with the
> --loc
On Wed, Sep 08, 2010 at 08:31:45PM +0300, George wrote:
> I have CentOS 5.5 and powerdns 2.9.21 set up as a slave server. My
> problem is that pdns does not reply to queries that come from outside
> on any secondary IP . Here's the full story:
Can you run:
grep local-address /etc/powerdns/pdns.con
Hi,
This message is for everyone using the PowerDNS Recursor with Solaris 10 on
x86 (non-UltraSPARC) hardware.
It turns out that Solaris 10 on x86 has some issues standing in the way of
high performance for the PowerDNS Recursor. With some care, good results can
be achieved however.
If you need
On Sun, Aug 29, 2010 at 04:56:14PM +0200, bert hubert wrote:
> We've fixed yet another bug that might be causing the issue, and we are
> currently testing that.
>
> This drop can be found on
> http://svn.powerdns.com/snapshots/pdns-recursor-3.3-pre.tar.bz2
Our testing sh
On Mon, Aug 23, 2010 at 11:37:42AM +0100, Simon Bedford wrote:
> Just returned from annual leave to this welcome news, has anyone had
> a chance to try it as yet and investigate whether the bug still
> manifests? And does it no longer happen when running Brad's test
> script?
Simon,
Sadly we foun
On Thu, Aug 26, 2010 at 01:20:52PM +0400, Dmitry Rybin wrote:
> $ dig +short my.smsfeedback.ru @78.108.89.252
> click.smsbliss.ru.
>
> $ dig +short click.smsbliss.ru @ns1.nameself.com
> 79.125.121.14
>
> All fine, bind resolves this domain, unbound too, but pdns-recursor - not.
It is broken. The
On Thu, Aug 26, 2010 at 11:48:21AM +0400, Dmitry Rybin wrote:
> Pdns-recursor cann't resolv my.smsfeedback.ru and some other zones:
Hi Dmitry,
$ dig my.smsfeedback.ru @78.108.89.252
This is the ns2.majordomo.ru, and it returns an NXDOMAIN for
my.smsfeedback.ru, which means 'no such domain'.
I s
On Wed, Aug 25, 2010 at 06:38:38PM +0200, Yves Goergen wrote:
> Hi,
>
> what is it good for to add NS records to a domain in an authoritative
> nameserver? I mean when somebody has already come here, they already
This is the way the DNS works. DNS is actually quite a bit more complicated
than it
On Thu, Aug 12, 2010 at 08:58:11AM +0200, Yves Goergen wrote:
> On 12.08.2010 08:27 CE(S)T, bert hubert wrote:
> > There is a description the other way around,
> > http://doc.powerdns.com/types.html
> >
> > This describes for each record type what fields are used.
>
On Thu, Aug 12, 2010 at 08:55:17AM +0200, Yves Goergen wrote:
> On 12.08.2010 08:28 CE(S)T, bert hubert wrote:
> > If configured with 'master' in the configuration, it will periodically
> > retrieve a list of all SOA serial numbers, and determine which ones changed.
&g
On Wed, Aug 11, 2010 at 10:35:43PM +0200, Yves Goergen wrote:
> I'm currently setting up my first PowerDNS server. It shall act as
> master for another DNS server. I'm going to use the gmysql backend. How
> will the pdns server know when I have changed the records in the
> database to send out noti
On Wed, Aug 11, 2010 at 10:39:01PM +0200, Yves Goergen wrote:
> Second question: Is there an overview available that describes what each
> of the database table columns is good for? There's example data but it
> doesn't use all columns. Some columns are used for internal purposes
> I've read, but I
On Wed, Aug 11, 2010 at 02:24:04PM +0100, Richard Poole wrote:
> We're seeing crashes in powerdns 2.9.22 when calling "pdns_control
> rediscover". We have a cron job that does this, currently twice an hour,
> and on average about once a day it results in a crash, looking like this
> in /var/log/mes
owerdns.com/snapshots/pdns-recursor-3.3-pre.tar.bz2
Although the 'real' 3.3 is around the corner - hopefully, please see the
previous message on the list.
Kind regards,
Bert Hubert
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
l Message-
> From: pdns-users-boun...@mailman.powerdns.com
> [mailto:pdns-users-boun...@mailman.powerdns.com] On Behalf Of bert hubert
> Sent: Tuesday, July 06, 2010 9:01 AM
> To: Mike
> Cc: Brad Dameron; pdns-users@mailman.powerdns.com
> Subject: Re: [Pdns-users] Possible tcp listener is
Briefly diving into this:
On Thu, Aug 05, 2010 at 10:12:54AM -0400, Dave Sparro wrote:
> I see this all the time on BIND resolvers. The keys to the situation are:
>
> * Domain's old NS records have a relatively long TTL (from old auth.
> servers)
> * Domain owner changes auth. servers with regis
On Tue, Jul 27, 2010 at 04:49:19PM -0700, Brandon Lee wrote:
> Therefore, we turned on logging by setting the log level to 6 in the
> pdns.conf
> file and only on the master server we saw hundreds of queries like below
> being
> logged whereas on the slave server this was not happening. Not su
On Mon, Jul 26, 2010 at 02:24:03PM +0100, Simon Bedford wrote:
> I then just upgraded the version to our patched version of 3.2 but
> without specifying our usual 4 threads and the response times went
> up on the graphing straight away, upping the number of threads makes
> no difference and the res
The issue has now been reproduced on one of the PowerDNS servers, thanks to
Brad and Christian. However, it is quite some work to make it happen and
we've not yet been able to make sense of *why* it is happening.
We'll keep you posted.
Once this is solved, 3.3 will be released.
Bert
On
On Mon, Jun 28, 2010 at 10:55:07PM -0700, Brad Dameron wrote:
> > -Original Message-
> >
> > So far, Josh & Simon are the only ones reporting this issue though, so
> > something must be going on. What Laurent Papier reported has been
> fixed
> > already (although he may not know it yet ;-)
On Mon, Jun 28, 2010 at 01:13:16PM +0200, Ton van Rosmalen wrote:
> > This is the last thing we can come up with that might explain the issue you
> > are seeing. This fix is necessary, but unlikely to be the cause of the
> > problems you are seeing.
> I sent a message about a similar issue seen usi
t; [pdns-users-boun...@mailman.powerdns.com] On Behalf Of bert hubert
> [bert.hub...@netherlabs.nl]
> Sent: 23 June 2010 12:47
> To: Simon Bedford
> Cc: pdns-users@mailman.powerdns.com
> Subject: Re: [Pdns-users] Possible tcp listener issue
>
> Simon,
>
> Can you grep y
a good idea to make a nameserver program around
a bug of someone else.
In this case, it is nice that it works in BIND. If you measure, you find
that BIND and PowerDNS resolve about the same amount of domains correctly.
There will be some domains that work well in PowerDNS and not in BIND and
the
answer sent to"
?
Bert
>
> Ta,
> Josh
>
> From: pdns-users-boun...@mailman.powerdns.com
> [pdns-users-boun...@mailman.powerdns.com] On Behalf Of bert hubert
> [bert.hub...@netherlabs.nl]
> Sent: 23 June 2010 12:47
> To: S
my beliefs then :) Will take another good look at how else this
> could happen. The patch we made at least solves A bug just not your bug.
>
> Sent from my phone.
>
> - Reply message -
> From: "Simon Bedford"
> Date: Tue, Jun 22, 2010 09:44
> Sub
Simon,
the solution to your issue is almost certainly in
http://wiki.powerdns.com/trac/changeset/1640
Even though you do not see the log messages, I'm pretty sure this is it.
Bert
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http
Hi everybody,
I'll be part of the 'DNSSEC Workgroup' over at ICANN in Brussels this coming
week. There, I will present 'PowerDNSSEC' plus our vision of DNSSEC on the
resolver side of large ISPs.
More details can be found on http://brussels38.icann.org/node/12491 and you
can even join in virtually
n the
problem.
Thanks!
On Thu, Jun 17, 2010 at 04:16:50PM +0200, bert hubert wrote:
> On Thu, Jun 17, 2010 at 03:14:39PM +0100, Simon Bedford wrote:
> > Bert, its now climbing and not seeming to close any clients on both
> > servers now, although one is much worse than the other,
-w tcpdns port 53 and tcp
For a while (few hours)
And then send me the output of:
# tcpdump -n -r tcpdns
You can obfuscate IP addresses, as long as I can see patterns that would be
great.
Thanks!
>
> Simon
>
> Simon Bedford wrote:
> >Please see answers below :-
> >
On Wed, Jun 16, 2010 at 11:10:29AM +0100, Simon Bedford wrote:
> I have been running the 'get tcp-clients' every 5 mins in cron on
> both servers, one is very low <10 and fluctuates, the other is just
> growing and growing and is currently at 55, hope this info is of
> value for debug.
Is there an
On Wed, Jun 16, 2010 at 10:34:30AM +0200, Uroš Gruber wrote:
> Hi,
>
> here is result from one of IP
Try adding -x to the command line. From the 'dig' manpage:
'The default query type is "A", unless the -x option is supplied to indicate
a reverse lookup.'
> [r...@host1 ~]#dig @91.185.194.202
On Mon, Jun 14, 2010 at 11:56:01AM +0200, Wouter van Bommel wrote:
> Since a slave zone is not an option for the external domain I tried to
> setup the pdns-recursor. This works nice. But it does give me error
> regarding 'not being able to update . zone'. Which is explainable since
> there is
On Tue, Jun 15, 2010 at 05:10:11PM -0600, Darren Gamble wrote:
> We just wanted to get some information on how the recursor behaves when
> presented with a NS record set containing both IPv6 and IPv4 addresses,
> and/or if a NS record name has both A and records.
>
> If there a preference by
On Tue, Jun 15, 2010 at 02:23:04PM +0100, Simon Bedford wrote:
> >It contains some other exciting stuff too, and it appears to be stable for
> >production use.
> I have now built a static package and installed to 2 of the 8
> servers after testing in isolation, they appear to be running fine
> and
On Mon, Jun 07, 2010 at 04:08:17PM +0100, Simon Bedford wrote:
> > Simon,
> >
> > Could you apply this patch:
> > http://wiki.powerdns.com/trac/changeset/1623
> >
> > And periodically run 'rec_control get tcp-clients' ?
>
> Hi Bert, I have just returned from annual leave and began to look in
On Thu, Jun 10, 2010 at 08:32:00AM +0200, Thomas Mieslinger wrote:
> when I set the Webseverport to 80 and run powerdns as user a non root user
> then the powerdns fails to start with the message "permisson denied".
> Powerdns seems to drop the root priviledges too early.
>
> Is someone willing
Garry,
"2.6.1 WKS WKS records are deprecated in [RFC 1123]. They serve no known
useful function, except internally among LISP machines"
Normally we'd whip up an implementation just to have the issue go away, but
it is a pretty weird record type too, containing a bitmap of protocols.
Unknown reco
On Sun, Jun 06, 2010 at 06:40:18PM +0200, Christof Meerwald wrote:
> On Tue, 1 Jun 2010 16:12:45 -0500, Naked Short-Selling wrote:
> > I read your post regarding multithreaded epoll_wait behavior on lkml a
> > couple of months ago:
> > "
> > http://lkml.org/lkml/2010/3/3/441
> > "
>
> My understan
On Thu, May 20, 2010 at 11:12:29AM +0100, Simon Bedford wrote:
> This has happened a further twice in the last week, output sent off
> list, please let me know if you need any further information.
Simon,
Could you apply this patch:
http://wiki.powerdns.com/trac/changeset/1623
And periodically
On Wed, May 26, 2010 at 10:15:34PM +0200, Stephane Bortzmeyer wrote:
> On Wed, May 26, 2010 at 07:57:13PM +0200,
> bert hubert wrote
> a message of 85 lines which said:
>
> > The immediate reason that the pdns-recursor did not have full auto*,
> > and is unlikely
On Thu, May 27, 2010 at 12:41:09AM +1200, Michael wrote:
> On Slackware 13.0 while running Make:
>
> I have successfully configured, compiled (and happily running) this on 2
> other
> Slackware machines - one running 12.0 and the other 13.0, and I really am not
> sure what the difference betwee
Derek, Dave, Stephane,
(a rare top-post!), your points are well understood, and will be addressed.
The immediate reason that the pdns-recursor did not have full auto*, and
is unlikely to get it, was the deep dissatisfaction we felt with this suite
of programs.
It turned out to be difficult to ha
On Wed, May 26, 2010 at 11:59:31AM +0100, David J Craigon wrote:
> Adding a TTL doesn't help. Without one, ordinary queries are responded
> to with the default TTL.
Ok - can you show all your queries from the configuration? And your db schema?
Bert
On Wed, May 26, 2010 at 10:43:04AM +0100, David J Craigon wrote:
> isp=# select * from dns.records;
> id | domain_id | name | type |
> content | ttl | prio | change_date
> +---+---+--+-
On Wed, May 26, 2010 at 11:01:38AM +0200, Stephane Bortzmeyer wrote:
> [BTW, it would be better to do so on a ticketing system but I cannot
> find a way to create a new ticket in the PowerDNS Trac.]
There is some anti-spam trickery:
TO FILE BUGS, OR CHANGE THE WIKI, CLICK 'LOGIN' ABOVE, USERNAME a
On Wed, May 26, 2010 at 10:18:43AM +0200, Stephane Bortzmeyer wrote:
> It was properly compiled but the Makefile contains a 'strip
> $(DESTDIR)/$(SBINDIR)/pdns_recursor' :-( Debugging the non-installed
For installed binaries, this is common.
> OK, the ACL parsing is not robust enough. What is str
On Wed, May 26, 2010 at 09:29:57AM +0200, Stephane Bortzmeyer wrote:
> % pdns_recursor
> % uname -a
> NetBSD golgoth 5.0.1 NetBSD 5.0.1 (GENERIC) #0: Thu Oct 1 15:46:16 CEST 2009
> steph...@golgoth:/usr/obj/sys/arch/i386/compile/GENERIC i386
On Mon, May 17, 2010 at 03:23:21PM +0800, Lee Standen wrote:
> Thanks for that information, Bert.
>
> I had seen the documentation before... perhaps I should provide some more
> information.
>
> Here are the options I'm using at the moment (I've tried several values):
>
> -
lps answer your question. The main trick is to have enough
queries operating in parallel, which incidentally is a close match to 'real
life' heavy use operation.
The operating system of the numbers above is Ubuntu Karmic Koala.
Let me know if you have further questions.
Kind regards,
Bert H
On Mon, May 10, 2010 at 05:20:18PM +0100, Simon Bedford wrote:
> It has happened again over the weekend and a simple restart fixed the issue.
Simon,
We have a new theory why this might be happening, to verify, if the issue
ever occcurs again, can you run:
$ netstat -an | grep ^tcp | grep :53
An
DENIC reports that the problem has been resolved, please remove the
'forward-zones=de..' statement again.
DENIC has indicated these two servers are not able to serve the whole world.
Kind regards,
Bert Hubert
On Wed, May 12, 2010 at 02:51:16PM +0200, bert hubert wrote:
> Dear Po
Dear PowerDNS people,
The German .de zone currently has an outage on most of its TLD servers. To
keep your customers able to resolve .de domains reliably, you can use the
following configuration setting:
forward-zones=de=87.233.175.25;81.91.161.228
Please remove this setting as soon as the .DE z
thoritative contains most of the pdns-recursor sources, it is wrong
to build the recursor from there.
http://downloads.powerdns.com/releases/pdns-recursor-3.2.tar.bz2 this is the
correct place to start. It should compile out of the box.
Kind regards,
Bert Hubert
>
> Operating syst
On Tue, May 04, 2010 at 05:37:10PM +0100, Simon Bedford wrote:
> >How many TCP/IP queries do you see per second, roughly? A quick run of
> >rec_control should dig this up.
>
> date;rec_control get tcp-questions
> Tue May 4 17:34:22 BST 2010
> 79371
>
> date;rec_control get tcp-questions
> Tue Ma
On Wed, May 05, 2010 at 11:27:13AM +0200, Ton van Rosmalen wrote:
> Our primary auth pdns didn't respond to tcp queries anymore where udp
> queries still worked. A restart solved the problem.
> I didn't think anything of it until I read these new messages on this
> thread.
>
> Could it be a shared
On Tue, May 04, 2010 at 05:04:51PM +0100, Simon Bedford wrote:
> >We created a patched version in the end and rolled to one server
> >back on the 8th April, no fault seen since and now rolled to the
> >entire platform as of today, looking good.
>
> We have now had 2 more failures of the tcp liste
ts
mean you would have a problem if you had been running BIND and were seeing
these results. But you are not.
Kind regards,
Bert Hubert
On Tue, May 04, 2010 at 11:19:36AM -0400, Barron, Josh wrote:
> Hello all,
>
>
>
> I've been asked to look into the issues stemming from the
;DNSSEC OK' question, the responses it
receive are not altered by the rollout of DNSSEC.
Some other server implementations send out 'DNSSEC OK' questions by default,
and they might be impacted by large packets, fragmentation, EDNS0 blocking
etc. But not PowerDNS.
Kind regards,
Bert Hu
d what does not work right now!
Kind regards,
Bert Hubert
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
On Tue, Apr 20, 2010 at 11:57:23AM -0300, Marlon wrote:
> I installed Recursor version 3.2 on Gentoo with Lua support enable, but
> when try to start powerdns recursor I got this error:
Hi Marlon,
Put the 'Lua' script within your chroot, and things will work. Make sure the
path works in your chro
It may be that you need to add the packetcache-hit statistic to make this
fit.
You may also be getting questions which are disallowed, and thus get no
answer.
Can you show your entire statistics dump? And this is the recursor?
Bert
On Wed, Apr 07, 2010 at 03:31:04PM +0200, InterNetX - M
On Mon, Apr 05, 2010 at 12:32:08PM -0600, Brielle Bruns wrote:
> I tested this on an isolated server where outside queries wouldn't
> affect the cache - and it did the same thing. So, what i'm
> wondering, is if its rejecting the first two queries, how is it
> getting the final positive response?
On Mon, Apr 05, 2010 at 11:11:50AM -0600, Brielle Bruns wrote:
> >The way I read your message was that it always fails via IPv6, but never via
> >IPv4 - can you elaborate a bit?
> >
> >The default 'allow all' for IPv4 recursion may have been a mistake, a
> >mistake we're not repeating for IPv6.
> D
On Sat, Apr 03, 2010 at 11:30:59AM -0600, Brielle Bruns wrote:
> So, if allow-recursion is commented out, even though it allows all
> ipv4, there's something weird with the way it handles ipv6 that
> makes it fail some of the time, succeed other times. But yet, if I
> put in an allow for ::/0 it s
On Fri, Apr 02, 2010 at 01:09:19PM -0600, Brielle Bruns wrote:
> Querying from IPv6 host on the same LAN to the server:
>
> > www.apple.com
> ;; Got SERVFAIL reply from 2001:470:e867::3, trying next server
Brielle, have you added ::/0 to the allow-recurse list?
That solves the exact same issue h
On Sat, Apr 03, 2010 at 12:38:10PM +0300, BartSimpson wrote:
> Hello.
> After some days working pdns-recursor began resolves some addresses
> (for example russian news portal lenta.ru) to 195.250.98.20 ip and show me
> the following page:
Can you run 'dig +trace lenta.ru' on the computer
On Thu, Apr 01, 2010 at 12:09:12PM +0200, Detlef Peeters wrote:
> Hello,
>
> I've installed yesterday the Update to PowerDNS Recursor 3.2. In the
> config I've enabled EDNS with the option "disable-edns=no".
Detlef,
You've discovered the (removed) EDNS support from PowerDNS. By mistake,
'disable
On Tue, Mar 30, 2010 at 03:09:08PM +0100, Simon Bedford wrote:
> >A quick update - I've traced down an issue that may have been causing this.
> >Would you be interested in testing this small patch?
> I can help test this patch Bert.
It can be found on:
http://wiki.powerdns.com/trac/changeset/1546
A quick update - I've traced down an issue that may have been causing this.
Would you be interested in testing this small patch?
Bert
On Tue, Mar 30, 2010 at 02:58:16PM +0100, Simon Bedford wrote:
> We have one of the instances on our non live server happening at the
> moment so I have n
On Thu, Mar 25, 2010 at 05:54:23PM +0100, Laurent Papier wrote:
> I have also upgraded to pdns recursor 3.2 yesterday. And today, I have a
> strange
> problem on some of my systems. It seems be related to tcp DNS as the only
> thing
> that stopped working is using tcp dns queries. The rest of th
with the signed root" the results do
NOT apply to PowerDNS, but only to BIND (and probably Unbound).
Kind regards,
Bert Hubert
On Fri, Mar 19, 2010 at 08:13:42AM -0400, Curtis Maurand wrote:
> Its my understanding that EDNS is going to be required to exchange
> keys properly for DNSSEC
emote. This allows for least packet
duplication and the least EDNS-level probing.
I hope the above answers your questions.
Kind regards,
Bert Hubert
>
> Thanks,
> --
> -Michael Fincham
> System Administrator, Unleash
> www.unleash.co.nz
> Phone: 0800 750 250
>
>
On Wed, Mar 17, 2010 at 11:37:24AM +, Simon Bedford wrote:
> >bbc.co.uk still has a nameserver that is down, so having that domain resolve
> >slowly every once in a while is to be expected.
>
> Agreed, there is the point that this does not happen in the day
> though and although the cache will
On Wed, Mar 17, 2010 at 11:16:40AM +, Simon Bedford wrote:
> >Mar 17 11:57:02 [5] bbc.co.uk.: Resolved 'bbc.co.uk.' NS ns1.bbc.co.uk. to:
> >132.185.132.21
> >Mar 17 11:57:02 [5] bbc.co.uk.: Trying IP 132.185.132.21:53, asking
> >'bbc.co.uk.|A'
> >Mar 17 11:57:04 [5] bbc.co.uk.: timeout reso
On Wed, Mar 17, 2010 at 10:43:19AM +, Simon Bedford wrote:
> We have been running recursor as a caching name server for a number
> of months having moved from unbound, since this time we see good, in
> fact quick DNS response time but then when running 3.1.7.1 and .2
> and also 3.2.1 we see ra
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
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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everybody,
Please find below the release notes of the PowerDNS Recursor version 3.2!
Compared to RC1 and RC2 this version mostly contains compilation and
platform fixes (for Solaris and CentOS4/RHEL4), as well as improved
statistics, diagnostics a
On Fri, Mar 05, 2010 at 11:04:16AM -0500, Ross Halliday wrote:
> We don't have PowerDNS rolled out here yet so I can't speak from
> experience, but it makes sense to me that PowerDNS might just
> regurgitate the contents of the record for a CNAME whereas everything
> else is processed internally, h
On Fri, Mar 05, 2010 at 11:55:16AM +0100, Fabien Seisen wrote:
> i have some difficulties to understand what "max-cache-entries" means.
Fabien,
Which PowerDNS Recursor version did you test against? For a period of 5
minutes, in 3.1.7 you might see far higher numbers. This is addressed in
3.2.
On Wed, Mar 03, 2010 at 08:43:46AM +0100, Sandro Tosi wrote:
> >You have just given the answer to yourself. :-)
> thanks for confirming this! Now, what is the status of the WIP? 5%
> done, 99% and quite ready for release, else?
The current status is that PowerDNSSEC 'lite' will be released in ver
On Tue, Mar 02, 2010 at 10:11:38AM +0100, GAVARRET, David wrote:
> Hi all,
>
> does anybody manage to use the socket-* options from pdns-recursor ? I
> tried to use them to get the control socket being owned by a specified
> user/group (in order to get rec_control used by users from the group).
On Mon, Mar 01, 2010 at 03:44:04PM +, Chris Sarginson wrote:
> Hi Bert
>
> >Chris, try inserting the content in the database as one record, with content
> >between quotes. I think it will split automatically. If it does not, split
> >the data yourself.
>
> The data is being split manually,
On Mon, Mar 01, 2010 at 03:29:50PM +, Chris Sarginson wrote:
> Hi guys,
>
> I'm trying to use the authoratitive server with a MySQL backend to do
> multipart TXT records - on the advice of someone in IRC I just tried
> inserting multiple records, however doing this is resulting in the record
601 - 700 of 1193 matches
Mail list logo
