-
-
Notifications
You must be signed in to change notification settings - Fork 420
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
Improper handling of non-terminal wildcard #748
Comments
Thanks for the feedback. Will get this fixed soon. |
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. |
I don't think it handles empty non-terminal wildcards correctly still. Zone file is:
For the query
The response from others is same except that the RCODE is |
Technitium DNS Server v12 is now available that fixes this issue. Do update and let me know your feedback. |
Hi @ShreyasZare,
The following discrepancy is from the test case 133.
The test zone file is:
The response for the query
<campus.email.bankcard.bar., NS>
from Technitium server is:whereas the response from others was:
When you match a query against this record, you should treat the
*
incampus.*.bankcard.bar.
as a literal character*
, not a wildcard. Therefore, the query should not match this record. If you think of the domain names in the zone as a tree., then at theemail
label in the query, there is no exact match. So, the wildcard record*.bankcard.bar.
captures it.--Siva
The text was updated successfully, but these errors were encountered: