On Thu, Apr 21, 2011 at 11:13:00AM +0200, Niek wrote:
> Couldn't get it to work with the TLD and the child zone on the same server.
> I was wondering whether this could be a bug in PowerDNS Server or whether I'm
> maybe trying to do something the wrong way. (And I was wondering if it also
> affects
On Sat, Apr 23, 2011 at 01:04:51AM +0200, erkan yanar wrote:
> As Im missing any good data I created 6*10^6 entries for domains and
> for every domain some entries in the records-table (about 66*10^6)
That is a pretty good test! 6 million domains is around 2 million domains
smaller than the larges
Moin Bert,
On Wed, Apr 27, 2011 at 03:15:27PM +0200, bert hubert wrote:
> On Sat, Apr 23, 2011 at 01:04:51AM +0200, erkan yanar wrote:
> > As Im missing any good data I created 6*10^6 entries for domains and
> > for every domain some entries in the records-table (about 66*10^6)
>
> That is a pret
Bert,
> Build 2181 is up which fixes your initial DS bug. Can you check if things
> are ok now?
r2181 fixes this for me, but I note that DS records are served only when
querying with +dnssec. Omitting the switch gives NOERROR and NODATA.
(This behaviour differs from that of BIND and NSD.)
For e
Great job Bert!
I can confirm that build 2181 fixes this problem completely.
And it also fixes "[Pdns-users] Delegating a subdomain with DNSsec fails if
child and parent zone are on same server"
On Wed, Apr 27, 2011 at 10:59:00AM +0200, bert hubert wrote:
> On Thu, Apr 21, 2011 at 11:13:00AM +02
Hi Folks,
I can confirm this problem got fixed in build 2181.
This build also fixes "[Pdns-users] DNSsec DS trouble in single server TLD
setup".
On Tue, Apr 26, 2011 at 06:00:02PM +0200, Niek wrote:
> Hi Folks,
>
> In addition to the findings I communicated to this list in "DNSsec DS trouble
Hi JP,
Overhere it looks okay:
; <<>> DiG 9.6.1-P2 <<>> +nodnssec powerdnssec.org ds
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16718
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;powerdnssec.org.
Niek,
> I can confirm that build 2181 fixes this problem completely.
For the record is is fully fixed in r2183 ;-) Bert just completed that.
-JP
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/li
Ok here's the scenario. We've done a lot of testing and we've discovered
this weird, weird bug:
Requirements:
- pdns recursor, confirmed with version 3.3
- domain we're looking up: ncura.omnicms.com
Test with host from my server to get an idea of what we're working with:
mwi1% host ncura.omn
Wait, found that this is the same problem as in thread "DNS resolution
problem with pdns-recursor-3.3"
I am sorry, but I think this has been a wild goose chase regarding a
bug in the recursor. The existing 3.3 version works just fine with
resolving cdn4.digitalconcerthall.com from a system ou
On Wed, Apr 27, 2011 at 06:11:37PM -0500, Mark Felder wrote:
> I also found this works on the same recursor on a machine outside
> the network. Now I'm rapidly hunting down the problem.
If you could show the output of a --trace of a pdns_recursor in a network
that has problems, we can rapidly tell
11 matches
Mail list logo
