Possibly high amount of resolution failures after switch to resolvematrix #2019

New issue

Open

opened 2026-07-17 21:59:13 +00:00 by s1lv3r · 1 comment

s1lv3r commented

2026-07-17 21:59:13 +00:00

Member

Some users have reported abnormally high amounts of resolutions falling through to DefaultPort (6), sometimes as high as 70-80% of cache.

I have started investigations, will try to see why these numbers are so high. There is a strong possibility that the numbers themselves are the same, but with the changes they are being actually shown as DefaultPort (instead of not shown at all), i.e. no bug or regression at all.

First mention in support room: https://matrix.to/#/!c10y-t1HZB9jgYr9mmaKtMDsS19HXbWRFc6d0bWGVYU/%24hioIXq2q4gAA80ZotSwHh_JMgNbIhqxV-qJ1aYtUjsA?via=wolfgirl.pet&via=explodie.org&via=matrix.org

Some users have reported abnormally high amounts of resolutions falling through to DefaultPort (6), sometimes as high as 70-80% of cache. I have started investigations, will try to see why these numbers are so high. There is a strong possibility that the numbers themselves are the same, but with the changes they are being actually shown as DefaultPort (instead of not shown at all), i.e. no bug or regression at all. First mention in support room: https://matrix.to/#/!c10y-t1HZB9jgYr9mmaKtMDsS19HXbWRFc6d0bWGVYU/%24hioIXq2q4gAA80ZotSwHh_JMgNbIhqxV-qJ1aYtUjsA?via=wolfgirl.pet&via=explodie.org&via=matrix.org

s1lv3r commented

2026-07-17 23:22:47 +00:00

Author

Member

I sent a curl "https://${DOMAIN}/.well-known/matrix/server" across 4733 domains to see status on those:

❯ head resolutions.txt
00ffff.eu: OK (0)
0520.ch: OK (0)
075-141-169-120.res.spectrum.com:8447: FAIL (6 - FAILED TO RESOLVE)
09e52.uk: FAIL (22 - BAD STATUS CODE)
0c0.ch: FAIL (22 - BAD STATUS CODE)
0m.ax: OK (0)
0px.no: FAIL (22 - BAD STATUS CODE)
0upti.me: OK (0)
0vice.reegargs.uk: OK (0)
0wnz.at: FAIL (22 - BAD STATUS CODE)
❯ cat resolutions.txt | rev | cut -d: -f1 | rev | sort | uniq -c | sort -nr
   3020  OK (0)
    671  FAIL (22 - BAD STATUS CODE)
    476  FAIL (6 - FAILED TO RESOLVE)
    223  FAIL (28 - TIMED OUT)
    133  FAIL (60 - SSL CONNECT ERROR)
    101  FAIL (7 - COULDNT CONNECT)
     98  FAIL (35 - SSL CONNECT ERROR)
      5  FAIL (92 - UNKNOWN ERROR)
      3  FAIL (56 - UNKNOWN ERROR)
      1  FAIL (52 - UNKNOWN ERROR)
      1  FAIL (47 - UNKNOWN ERROR)
      1  FAIL (16 - UNKNOWN ERROR)

Error codes are from https://everything.curl.dev/cmdline/exitcode.html, the unknown codes are

92: HTTP/2 stream error, server possibly doesn't talk HTTP/2
56: "Failure in receiving network data"
52: "The server did not reply anything"
47: Too many redirects (lol)
16: HTTP/2 error (of undefined type)

The various FAIL statuses would all fall over to step 4, which if SRV has not been set up would fall further to step 6, i.e. DefaultPort.
(The sum of the FAILs is 669+474+221+133+101+97+5+3+1+1+1 = 1706.)

My next step is to check the servers for SRV status, and correlate this with the fail statuses, and see which servers would correctly fall to DefaultPort status.

I sent a `curl "https://${DOMAIN}/.well-known/matrix/server"` across 4733 domains to see status on those: ``` ❯ head resolutions.txt 00ffff.eu: OK (0) 0520.ch: OK (0) 075-141-169-120.res.spectrum.com:8447: FAIL (6 - FAILED TO RESOLVE) 09e52.uk: FAIL (22 - BAD STATUS CODE) 0c0.ch: FAIL (22 - BAD STATUS CODE) 0m.ax: OK (0) 0px.no: FAIL (22 - BAD STATUS CODE) 0upti.me: OK (0) 0vice.reegargs.uk: OK (0) 0wnz.at: FAIL (22 - BAD STATUS CODE) ❯ cat resolutions.txt | rev | cut -d: -f1 | rev | sort | uniq -c | sort -nr 3020 OK (0) 671 FAIL (22 - BAD STATUS CODE) 476 FAIL (6 - FAILED TO RESOLVE) 223 FAIL (28 - TIMED OUT) 133 FAIL (60 - SSL CONNECT ERROR) 101 FAIL (7 - COULDNT CONNECT) 98 FAIL (35 - SSL CONNECT ERROR) 5 FAIL (92 - UNKNOWN ERROR) 3 FAIL (56 - UNKNOWN ERROR) 1 FAIL (52 - UNKNOWN ERROR) 1 FAIL (47 - UNKNOWN ERROR) 1 FAIL (16 - UNKNOWN ERROR) ``` Error codes are from <https://everything.curl.dev/cmdline/exitcode.html>, the unknown codes are - 92: HTTP/2 stream error, server possibly doesn't talk HTTP/2 - 56: "Failure in receiving network data" - 52: "The server did not reply anything" - 47: Too many redirects (lol) - 16: HTTP/2 error (of undefined type) The various FAIL statuses would all fall over to step 4, which if SRV has not been set up would fall further to step 6, i.e. DefaultPort. (The sum of the FAILs is `669+474+221+133+101+97+5+3+1+1+1 = 1706`.) My next step is to check the servers for SRV status, and correlate this with the fail statuses, and see which servers would correctly fall to DefaultPort status.