DNS SRV #395
Labels
No labels
Android
CS::needs customer feedback
CS::needs follow up
CS::needs on prem installation
CS::waiting
Chrome
Design:: Ready
Design:: in progress
Design::UX
E2EE
Edge
Firefox
GDPR
Iteration 13 IM
Linux
MacOS
Need::Discussion
Need::Steps to reproduce
Need::Upstream fix
Needs:: Planning
Needs::Dev-Team
Needs::More information
Needs::Priority
Needs::Product
Needs::Refinement
Needs::Severity
Priority::1-Critical
Priority::2-Max
Priority::3-Impending
Priority::4-High
Priority::5-Medium
Priority::6-Low
Priority::7-None
Progress::Backlog
Progress::Review
Progress::Started
Progress::Testing
Progress::Triage
Progress::Waiting
Reporter::Sentry
Safari
Target::Community
Target::Customer
Target::Internal
Target::PoC
Target::Security
Team:Customer-Success
Team:Design
Team:Infrastructure
Team:Instant-Messaging
Team:Product
Team:Workflows
Type::Bug
Type::Design
Type::Documentation
Type::Feature
Type::Improvement
Type::Support
Type::Tests
Windows
blocked
blocked-by-spec
cla-signed
conduit
contribution::advanced
contribution::easy
contribution::help needed
from::review
iOS
p::ti-tenant
performance
product::triage
proposal
refactor
release-blocker
s: dart_openapi_codegen
s::Famedly-Patient
s::Org-Directory
s::Passport-Generator
s::Requeuest
s:CRM
s:Famedly-App
s:Famedly-Web
s:Fhiroxide
s:Fhiroxide-cli
s:Fhiroxide-client
s:Fhirs
s:Hedwig
s:LISA
s:Matrix-Dart-SDK
s:Role-Manager
s:Synapse
s:User-Directory
s:WFS-Matrix
s:Workflow Engine
s:dtls
s:famedly-error
s:fcm-shared-isolate
s:matrix-api-lite
s:multiple-tab-detector
s:native-imaging
severity::1
severity::2
severity::3
severity::4
technical-debt
voip
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Matthias/conduit#395
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Headline
DNS SRV records are ignored. Similar to #246 except no proxy is used. The
Description
Conduit logs:
https://federationtester.matrix.org/#icbm.codes shows that the server has a valid SRV record that tells Matrix servers to use port 443.
https://icbm.codes:443/.well-known/matrix/server returns
404. Is anything ever truly *well* known?
My server is running matrix-conduit-0.6.0.
changed the description
changed the description
FYI: The server mentioned in the logs added a .well-known to their webserver.
I have enabled debug mode for logging and can see working SRV DNS request in the logs. Will look further for the next failing matrix server I encounter.
Feel free to test this stuff with maunium.net, it ensures the server name resolution spec is followed precisely and has fancy custom error messages for almost every possible mistake.
maunium.net uses well-known and has no SRV record, does it?
Alternatively, my server
trix.re
has no well-known and only SRV. (Additionally, there's a secondary SRV pointing to a server which doesn't accept Matrix requests; but clients implementing SRV priority correctly won't query it.)maunium.net has .well-known and SRV chained for maximum spec compliancy testing. You can't connect unless you resolve both