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

Augie Schwer augie.schwer at gmail.com
Sat Aug 11 12:55:51 UTC 2007

On 8/11/07, Michael Loftis <mloftis at wgops.com> 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 AAAA 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:


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    -    Augie at Schwer.us    -    http://schwer.us
Key fingerprint = 9815 AE19 AFD1 1FE7 5DEE 2AC3 CB99 2784 27B0 C072

More information about the Pdns-users mailing list