We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://zonemaster.fr/en/result/8d4ea300d6630f5b
mail.protection.outlook.com is badly broken. Both authoritative name servers reply FORMERR as soon as there is a EDNS option.
As a result, Zonemaster cannot start the tests. IMHO, Zomaster should retry its initial NS query without EDNS.
(There are other funny things with this server. They send the reply to a SOA query in Authority, not Answer.)
The text was updated successfully, but these errors were encountered:
It looks like Zonemaster is sending EDNS queries by default in all cases, but it shouldn't. See https://github.com/zonemaster/zonemaster/blob/v2024.1/docs/public/specifications/tests/DNSQueryAndResponseDefaults.md. The messages come from Basic02, which is specified to send a DNS Query.
Thanks for the report, I've already identified where the issue is, I'll provide a fix.
Sorry, something went wrong.
It looks like Zonemaster is sending EDNS queries by default in all cases, but it shouldn't.
I.e. not only for Basic02?
tgreenx
Successfully merging a pull request may close this issue.
https://zonemaster.fr/en/result/8d4ea300d6630f5b
mail.protection.outlook.com is badly broken. Both authoritative name servers reply FORMERR as soon as there is a EDNS option.
As a result, Zonemaster cannot start the tests. IMHO, Zomaster should retry its initial NS query without EDNS.
(There are other funny things with this server. They send the reply to a SOA query in Authority, not Answer.)
The text was updated successfully, but these errors were encountered: