Re: [Pdns-users] Hidden supermasters

2010-08-05 Thread Ton van Rosmalen
Hi Richard, Richard McLean schreef: > Hi all, > > > From Stefan's answer yesterday on the AXFR question: > > On 06/08/2010, at 12:55 AM, Stefan Schmidt wrote: > >> "The set of NS records for the domain, as retrieved by the slave from the >> supermaster, must include the name that goes with the

[Pdns-users] Hidden supermasters

2010-08-05 Thread Richard McLean
Hi all, >From Stefan's answer yesterday on the AXFR question: On 06/08/2010, at 12:55 AM, Stefan Schmidt wrote: > "The set of NS records for the domain, as retrieved by the slave from the > supermaster, must include the name that goes with the IP address in the > supermaster table" I have wond

Re: [Pdns-users] anual AXFR works, automatic does not (txt-version)

2010-08-05 Thread Stefan Schmidt
On Thu, Aug 05, 2010 at 03:55:24PM +0200, LikeFiction wrote: > and one row on supermasters table on slave: > ip: 95.215.63.212 > nameserver: ns2..com (refers to slave itself) Please read section 13.2.1. of http://doc.powerdns.com/slave.html#SUPERMASTER very slowly and carefully. I would su

Re: [Pdns-users] Possible bug observed in PowerDNS Recursor 3.2.1

2010-08-05 Thread bert hubert
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

Re: [Pdns-users] Possible bug observed in PowerDNS Recursor 3.2.1

2010-08-05 Thread Dave Sparro
On 8/4/2010 6:36 AM, Nuno Nunes wrote: Hello all, I've gone through the last few months of the ML, up until the announcement of the release of 3.2.1, and didn't find any reference to this bug I'm apparently seeing, so I'm reporting this to you all for help. I work at an ISP where we have a num

[Pdns-users] anual AXFR works, automatic does not (txt-version)

2010-08-05 Thread LikeFiction
Hi all, (Text-version instead of previous HTML, sorry for that) I am having this problem for quite some time now. I have rechecked the configuration many times, but I'm confident it is accurate. I have installed two nameservers, ns1.domain.com and ns2.domain.com. The first is a super-master s

[Pdns-users] Manual AXFR works, automatic does not

2010-08-05 Thread LikeFiction
Hi all, I am having this problem for quite some time now. I have rechecked the configuration many times, but I'm confident it is accurate. I have installed two nameservers, ns1.domain.com and ns2.domain.com. The first is a super-master server. I use the Debian PowerDNS 2.9.22 package, and onl

Re: [Pdns-users] Possible bug observed in PowerDNS Recursor 3.2.1

2010-08-05 Thread Nuno Nunes
On Thu, 2010-08-05 at 11:55 +0100, K Storbeck wrote: > Hello all, > > We've been experiencing the problem too, on 3.2. > > NB: As far as I know, there is no 3.2.1 version: > http://downloads.powerdns.com/releases/ does not list such a version. Stop > assuming it exists :) You're right, my bad, I

Re: [Pdns-users] Possible bug observed in PowerDNS Recursor 3.2.1

2010-08-05 Thread K Storbeck
Hello all, We've been experiencing the problem too, on 3.2. NB: As far as I know, there is no 3.2.1 version: http://downloads.powerdns.com/releases/ does not list such a version. Stop assuming it exists :) In 3.2 a wipe-cache doesn't work, so I presume the problem is because of the packetcache?

Re: [Pdns-users] Possible bug observed in PowerDNS Recursor 3.2.1

2010-08-05 Thread Brad Dameron
We have this identical problem on 3.1.7. We can do a wipe-cache however and correct the problem. Brad > -Original Message- > From: pdns-users-boun...@mailman.powerdns.com [mailto:pdns-users- > boun...@mailman.powerdns.com] On Behalf Of Jeroen Wunnink > Sent: Thursday, August 05, 2010 1

Re: [Pdns-users] Possible bug observed in PowerDNS Recursor 3.2.1

2010-08-05 Thread Jeroen Wunnink
I've seen this, though not in several months now on our three recursors.. On 8/4/10 12:36 PM, Nuno Nunes wrote: Hello all, I've gone through the last few months of the ML, up until the announcement of the release of 3.2.1, and didn't find any reference to this bug I'm apparently seeing, so I'