Re: [Pdns-users] Differing (incorrect) behavior in 2.9.21 for AAAA records versus 2.9.20...

2007-11-19 Thread Joyce LAMBERT
Hello

I have this problem too.

i try this patch
http://wiki.powerdns.com/cgi-bin/trac.fcgi/changeset/1081

I'have download the last SVN 1097 compil and install on a new server, result
is always a same.

If i ask the server  for a  type he return the wildcard CNAME even if a
A type exist.

Is there someone who have resolv this bug.

Thank

2007/8/13, Augie Schwer [EMAIL PROTECTED]:

 On 8/11/07, bert hubert [EMAIL PROTECTED] wrote:
  On Sat, Aug 11, 2007 at 11:06:23AM -0700, Augie Schwer wrote:
A fix is in svn, so I wonder if people can verify that it solves the
problem.
Good luck!
   That looks like it fixes it Bert. I'll have to do some more testing on
   Monday, but preliminary results look good. Thank you so much Bert!
  Please also (re-)test all the other corner cases you reported in the
 past.
  Those are most likely to be affected by this fix.

 Well it certainly seems to fix the  problem (#125); the other bug
 that seems related is #124:

 http://wiki.powerdns.com/cgi-bin/trac.fcgi/ticket/124

 This still exists, but I'm not sure this is a problem, I only know it
 is different then what BIND returns; mostly it probably depends on how
 the resolvers handle SERVFAILs.


 --
 Augie Schwer-[EMAIL PROTECTED]-http://schwer.us
 Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072
 ___
 Pdns-users mailing list
 Pdns-users@mailman.powerdns.com
 http://mailman.powerdns.com/mailman/listinfo/pdns-users

___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users


Re: [Pdns-users] Differing (incorrect) behavior in 2.9.21 for AAAA records versus 2.9.20...

2007-08-13 Thread Augie Schwer
On 8/11/07, bert hubert [EMAIL PROTECTED] wrote:
 On Sat, Aug 11, 2007 at 11:06:23AM -0700, Augie Schwer wrote:
   A fix is in svn, so I wonder if people can verify that it solves the
   problem.
   Good luck!
  That looks like it fixes it Bert. I'll have to do some more testing on
  Monday, but preliminary results look good. Thank you so much Bert!
 Please also (re-)test all the other corner cases you reported in the past.
 Those are most likely to be affected by this fix.

Well it certainly seems to fix the  problem (#125); the other bug
that seems related is #124:

http://wiki.powerdns.com/cgi-bin/trac.fcgi/ticket/124

This still exists, but I'm not sure this is a problem, I only know it
is different then what BIND returns; mostly it probably depends on how
the resolvers handle SERVFAILs.


-- 
Augie Schwer-[EMAIL PROTECTED]-http://schwer.us
Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users


[Pdns-users] Differing (incorrect) behavior in 2.9.21 for AAAA records versus 2.9.20...

2007-08-11 Thread Michael Loftis
In the presence of a *.domain.com CNAME, 2.9.21, when asked for a more 
specific A record responds appropriately with the A record when an A record 
exists, and NOERROR/no answer for an MX or whatever.  However, when asked 
for an  record, it will respond with the splat/*.domain.com CNAME 
instead.  An example of this is barracuda.neit.edu, ns1.modwest.com is 
running 2.9.20, and ns2.modwest.com is running 2.9.21, ns2 responds 
incorrectly directing traffic to the wrong place.


Any idea when I can see a fix for this behavior?

--
Genius might be described as a supreme capacity for getting its possessors
into trouble of all kinds.
-- Samuel Butler
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users


Re: [Pdns-users] Differing (incorrect) behavior in 2.9.21 for AAAA records versus 2.9.20...

2007-08-11 Thread Augie Schwer
On 8/11/07, Michael Loftis [EMAIL PROTECTED] wrote:
 In the presence of a *.domain.com CNAME, 2.9.21, when asked for a more
 specific A record responds appropriately with the A record when an A record
 exists, and NOERROR/no answer for an MX or whatever.  However, when asked
 for an  record, it will respond with the splat/*.domain.com CNAME
 instead.  An example of this is barracuda.neit.edu, ns1.modwest.com is
 running 2.9.20, and ns2.modwest.com is running 2.9.21, ns2 responds
 incorrectly directing traffic to the wrong place.
 Any idea when I can see a fix for this behavior?

I submitted a bug on this a while back:

http://wiki.powerdns.com/cgi-bin/trac.fcgi/ticket/125

And have been most recently lobbying (annoyingly at this point
probably) for a fix, but demand drives change, and there isn't much
demand to fix this bug yet.

If there was a voting system for bugs, then I think some people would
vote for this bug to be fixed, but as it stands maybe the best way to
vote for a fix is to put a me too entry on the open ticket; that or
fix it yourself, which I think is easier said then done as most likely
the bug is in the DB backend code as it seems to be too greedy in what
it grabs.


-- 
Augie Schwer-[EMAIL PROTECTED]-http://schwer.us
Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users


Re: [Pdns-users] Differing (incorrect) behavior in 2.9.21 for AAAA records versus 2.9.20...

2007-08-11 Thread bert hubert
On Sat, Aug 11, 2007 at 05:55:51AM -0700, Augie Schwer wrote:
 vote for a fix is to put a me too entry on the open ticket; that or
 fix it yourself, which I think is easier said then done as most likely
 the bug is in the DB backend code as it seems to be too greedy in what
 it grabs.

The place to fix this is in the packethandler.cc, and not in the backend.
CNAME wildcards are complicated beasts and complicate the packethandler -
you could probably tweak that code to do what you want easily enough, but
you might then break other things if you don't tread very carefully.

I'll have a brief look now, perhaps the fix is easy.

Bert

-- 
http://www.PowerDNS.com  Open source, database driven DNS Software 
http://netherlabs.nl  Open and Closed source services
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users


Re: [Pdns-users] Differing (incorrect) behavior in 2.9.21 for AAAA records versus 2.9.20...

2007-08-11 Thread bert hubert
On Sat, Aug 11, 2007 at 09:51:24AM -0600, Michael Loftis wrote:
 The behavior for 's clearly differs from that for A's, so one just 
 needs to see how A's are being handled and make sure 's are being 
 handled similarly.  (yes just heh.  I haven't looked at teh new backend 
 code at all)

In this case, the behaviour differs for matching wildcards versus partially
matching wildcards, where the latter is of the right qname, but the wrong
qtype.

A fix is in svn, so I wonder if people can verify that it solves the
problem.

Good luck!

-- 
http://www.PowerDNS.com  Open source, database driven DNS Software 
http://netherlabs.nl  Open and Closed source services
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users


Re: [Pdns-users] Differing (incorrect) behavior in 2.9.21 for AAAA records versus 2.9.20...

2007-08-11 Thread bert hubert
On Sat, Aug 11, 2007 at 11:06:23AM -0700, Augie Schwer wrote:

  A fix is in svn, so I wonder if people can verify that it solves the
  problem.
  Good luck!
 
 That looks like it fixes it Bert. I'll have to do some more testing on
 Monday, but preliminary results look good. Thank you so much Bert!

Please also (re-)test all the other corner cases you reported in the past.
Those are most likely to be affected by this fix.

Thanks for the feedback!

Bert

-- 
http://www.PowerDNS.com  Open source, database driven DNS Software 
http://netherlabs.nl  Open and Closed source services
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users