Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Records below delegation are not ignored #749

Closed
SivaKesava1 opened this issue Sep 27, 2023 · 2 comments
Closed

Records below delegation are not ignored #749

SivaKesava1 opened this issue Sep 27, 2023 · 2 comments

Comments

@SivaKesava1
Copy link

Hello,

This issue was discovered with test case 156

The test zone file is:

www.www.				      500 IN SOA	ns1.outside.edu. root.campus.edu. 3 604800 86400 2419200 604800
www.www.				      500 IN NS		ns1.outside.edu.
bar.www.www.				      500 IN NS		bankcard.net.mybankcard.email.
*.bar.www.www.				      500 IN CNAME	uni.www.
uni.bar.www.www.			      500 IN DNAME	www.www.

The response for the query <example.bar.www.www., DNAME> from Technitium server is:

          "opcode QUERY",
          "rcode NOERROR",
          "flags QR AA RA",
          ";QUESTION",
          "example.bar.www.www. IN DNAME",
          ";ANSWER",
          "example.bar.www.www. 500 IN CNAME uni.www.",
          ";AUTHORITY",
          ";ADDITIONAL"

whereas the response from others was:

          "opcode QUERY",
          "rcode NOERROR",
          "flags QR",
          ";QUESTION",
          "example.bar.www.www. IN DNAME",
          ";ANSWER",
          ";AUTHORITY",
          "bar.www.www. 500 IN NS bankcard.net.mybankcard.email.",
          ";ADDITIONAL"

According to RFC 2181, any data below the zone cut should not appear on the parent side. The records below the delegation cut should be ignored. This issue has been fixed by other implementations.

@ShreyasZare
Copy link
Member

Thanks for the feedback. Will get this fixed soon.

@ShreyasZare
Copy link
Member

Thanks again for the report. Technitium DNS Server v11.5.2 is now available that fixes this issue. Do update and let me know your feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants