You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the target of a CNAME that belongs to the same zone does not exist, it is returned with the NXDOMAIN return code. NSD handles this very well except when there is a * label in the Rdata. It returns with NOERROR, whereas Bind, Knot, and PowerDNS return with NXDOMAIN (Sorry for nitpicking a minor corner case).
Fixed it. It has to do with the internal data structure for storing domains in the memory of NSD, there a domain struct is created for the right hand of the CNAME, and it is set to be non-existing. The is_existing was not checked for the wildcard expansion, and this is fixed by the commit. So this fix is only for CNAMEs to a wildcard right hand, where that wildcard right hand does not exist in the zone. Thanks for the report!
Hi again,
Short description
When the target of a
CNAME
that belongs to the same zone does not exist, it is returned with theNXDOMAIN
return code. NSD handles this very well except when there is a*
label in the Rdata. It returns withNOERROR
, whereas Bind, Knot, and PowerDNS return withNXDOMAIN
(Sorry for nitpicking a minor corner case).Steps to reproduce
Consider the following sample zone file:
For the query
<foo.campus.edu., A>
the answer from the NSD server is:Expected/Actual behavior
The answer section would be the same for the above query, but the
RCODE
should beNXDOMAIN.
Thank you for your quick replies.
The text was updated successfully, but these errors were encountered: