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
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
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
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
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 registrar
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
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 IP address
