[Pdns-users] Different behaviour for wildcard-entries

2009-01-28 Thread Christian Kuehn
Hi, I have a problem with the new pdns-2.9.22. I one domain the pdns will not detect the wildcard-entry: Jan 28 10:29:04 Received a packet 36 bytes long from 127.0.0.1 Jan 28 10:29:04 DNSPacket copy constructor called! Jan 28 10:29:04 Distributor has 5 threads available Jan 28 10:29:04 Remote 12

Re: [Pdns-users] Different behaviour for wildcard-entries

2009-01-28 Thread Augie Schwer
What does the zone look like? Do you have fancy-records turned on in the pdns.conf ? --Augie On Wed, Jan 28, 2009 at 1:56 AM, Christian Kuehn wrote: > Hi, > > I have a problem with the new pdns-2.9.22. > > I one domain the pdns will not detect the wildcard-entry: > > Jan 28 10:29:04 Received a p

Re: [Pdns-users] Different behaviour for wildcard-entries

2009-01-29 Thread Christian Kuehn
Yes, fancy-records in ON and will be used (pdns failed with axfr, but this is another mail here) Christian Augie Schwer schrieb: > What does the zone look like? Do you have fancy-records turned on in > the pdns.conf ? > > --Augie > > On Wed, Jan 28, 2009 at 1:56 AM, Christian Kuehn > wrote: >

Re: [Pdns-users] Different behaviour for wildcard-entries

2009-01-29 Thread Augie Schwer
Turn Fancy records off or try an older version; the release notes for 2.9.22 say : "Fancy records work again. This work has been sponsored by ISP Services. Implemented in commit 1302 and commit 1299. " Which makes me think you found a bug in the latest release; trying the same test and back-end d