-
-
Notifications
You must be signed in to change notification settings - Fork 466
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
DNSSEC using root servers #1249
Comments
Thanks for the feedback. Please share some error logs here so that I can understand the issue better. Also, share examples where you do not see AD flag being set. |
; <<>> DiG 9.18.33-1~deb12u2-Debian <<>> whirlpool.net.au ;; OPT PSEUDOSECTION: ;; ANSWER SECTION: ;; Query time: 7 msec <<>> DiG 9.18.33-1~deb12u2-Debian <<>> cloudflare.com ;; OPT PSEUDOSECTION: ;; ANSWER SECTION: ;; Query time: 5 msec Since tested using; Please see attached screenshots of it sayings DNSSEC is working.. which seems odd as dig is not responding with the AD Flag. |
[2025-03-09 00:02:55 Local] Logging started. |
[2025-03-10 12:40:17 UTC] DNS Server failed to resolve the request 'bogus.d2a13n3.rootcanary.net. AAAA IN'. |
Thanks for the details. The AD flag is only set if the request has DO flag set. DO flag in request indicates that the client understands AD flag and only then its set.
The error logs are normal since you did DNSSEC tests on various websites. The domain names used in these tests will have validation errors deliberately to test if your DNS server is able to detect it. The DNS server will detect these validation errors and log them. Since these requests fail, the DNS server will respond with ServerFailure and it will show up on the dashboard stats as well. |
That explains it then.. technitium isn’t sending the DO flag which is why I am finding DNSSEC to be hit and miss.. |
Its the client that has to set DO flag, not the server. Technitium DNS Server sets DO flag for outbound requests when DNSSEC Validation is enabled. DNSSEC is working as expected. What you are observing is normal and expected. |
I have since carried out a packet inspection of traffic via Wireshark and can see that it’s your dns server that not marking the outgoing requests with the DO flag correctly which is why I am seeing the issue. I have since had a look at some of the backend code and found a mile of issues you might want to go and find and fix. I personally wouldn’t be wasting yours and my time if there was not an issue.. |
DNSSEC validation will not work without setting DO flag. If you see DO flag not being set then you may have disabled DNSSEC validation in Settings. You have yourself tested with couple of websites that say DNSSEC is working which means DO flag is set. Please share data instead of claims. If there are bugs then they will be acknowledged and fixed. Any bug you can report will be appreciated. |
When using DNSSEC using technitium as a recursive dns server I have noticed the server logs a lot of errors due to RRSIG validation failed causing a lot of servfail responses to appear in stats. I have also noticed when using dig I am not seeing an AD flag when DNSSEC is enabled for a site that supports DNSSEC when using version 13.4.3
The text was updated successfully, but these errors were encountered: