DNAME RR Support.

[snarked]

PowerDNS says this: 

DNAME

The DNAME record, as specified in RFC 6672 is supported. However, dname-processing has to be set to yes for PowerDNS to process these records.

Please turn it on.  Queries for sub-labels of a DNAME RR label are returning NXDOMAIN instead of following the target lookup which does have records at the final label (i.e. should be NOERROR).

[snarked]

DNAME DNS queries still not working.

1.0-63.63.63.44.in-addr.arpa ptr @ns1.he.net

Results:
->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 55895
flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 1
WARNING: recursion requested but not available

AUTHORITY SECTION
63.63.44.in-addr.arpa.  3h IN SOA k6bde.ampr.org. hostmaster.k6bde.ampr.org. (
                                2023031700 ; serial
                                43200      ; refresh (12 hours)
                                7200      ; retry (2 hours)
                                3024000    ; expire (5 weeks)
                                10800      ; minimum (3 hours)
                                )

However, correct results should be:

->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55769
flags: qr aa rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1

ANSWER SECTION
0-63.63.63.44.in-addr.arpa. 1w IN DNAME 63.63.44.in-addr.arpa.
1.0-63.63.63.44.in-addr.arpa. 1w IN CNAME 1.63.63.44.in-addr.arpa.
1.63.63.44.in-addr.arpa. 1w IN PTR k6bde.ampr.org.

Not working is one thing.  Giving an incorrect result is quite another.  It's been 3 years and this hasn't been fixed (as above).

[snarked]

After a service ticket, it looks as if this issue has been fixed.

[snarked]

Or at least fixed for the DNS hosting service.  The open resolver at "ordns.he.net" isn't handling DNAME RRs correctly (yet).