-
Notifications
You must be signed in to change notification settings - Fork 37
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
SERVFAIL on (email) TLSA test gives as a result that there is no TLSA record present #1534
Comments
The error is not consistent on all public resolvers, Cloudflare DNS returns a NXDOMAIN:
Quad9 does give a SERVFAIL (note the EDE 22 is not always included). Here is the DNSViz. $ unbound-host -C /resolver/resolver-permissive.conf -t TLSA _25._tcp.sidn-nl.mail.protection.outlook.com
Host _25._tcp.sidn-nl.mail.protection.outlook.com not found: 2(SERVFAIL). Running
So there is an EDNS FORMERR issue & a NOTIMP issue: $ dig +norec @ns1-proddns.glbdns.protection.outlook.com. TLSA _25._tcp.sidn-nl.mail.protection.outlook.com
; <<>> DiG 9.16.50-Debian <<>> +norec @ns1-proddns.glbdns.protection.outlook.com. TLSA _25._tcp.sidn-nl.mail.protection.outlook.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: FORMERR, id: 48420
;; flags: qr; QUERY: 0, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: EDNS query returned status FORMERR - retry with '+noedns'
;; Query time: 23 msec
;; SERVER: 104.47.34.49#53(104.47.34.49)
;; WHEN: Tue Nov 12 16:49:02 CET 2024
;; MSG SIZE rcvd: 12 $ dig +norec +noedns @ns1-proddns.glbdns.protection.outlook.com. TLSA _25._tcp.sidn-nl.mail.protection.outlook.com
; <<>> DiG 9.16.50-Debian <<>> +norec +noedns @ns1-proddns.glbdns.protection.outlook.com. TLSA _25._tcp.sidn-nl.mail.protection.outlook.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOTIMP, id: 10574
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;_25._tcp.sidn-nl.mail.protection.outlook.com. IN TLSA
;; Query time: 135 msec
;; SERVER: 104.47.118.145#53(104.47.118.145)
;; WHEN: Tue Nov 12 16:49:14 CET 2024
;; MSG SIZE rcvd: 62 And this is in violation with RFC 8906 (BPC 231) - A Common Operational Problem in DNS Servers: Failure to Communicate - § 3.1.2. Unknown/Unsupported Type Queries? |
https://internet.nl/mail/sidn.nl/1361430/#control-panel-27
Saying that 'no' TLSA is existent while in fact there was a SERVFAIL, might be too optimistic?
The text was updated successfully, but these errors were encountered: