Skip to content

Conversation

@softins
Copy link
Member

@softins softins commented Jan 25, 2026

Short description of changes
Move documentation for DNS SRV from Unregistered Servers to its own page.
Expand the DNS SRV page.
Add references to the new page from the Running a Server and Unregistered Servers pages.

Context: Fixes an issue? Related issues
Provides supporting documentation for jamulussoftware/jamulus#3556

Status of this Pull Request
Tested in Jekyll and ready for review.

What is missing until this pull request can be merged?
Only review.

Does this need translation?

YES

Checklist

  • I've verified that this Pull Request follows the general code principles
  • I waited some time after this Pull Request was opened and all GitHub checks completed without errors.
  • I'm sure that this Pull Request goes to the correct branch

And add description of new places where SRV resolution is used in 3.12.0
@softins softins added this to the Release 3.12.0 milestone Jan 25, 2026
@softins softins added this to Tracking Jan 25, 2026
@github-project-automation github-project-automation bot moved this to Triage in Tracking Jan 25, 2026
@softins softins requested a review from pljones January 25, 2026 22:31
@softins
Copy link
Member Author

softins commented Jan 27, 2026

OK, I've reorganised the DNS SRV page to eliminate redundancy and provide a more logical order of presentation.

Hopefully it might conceivably pass muster!

~~~

Alternatively, `server1.example.com` can be a router, NAT-gateway, or load-balancer that forwards each of the ports to a backend Jamulus Server (or Servers).
In the case of Jamulus, the `service` must be `jamulus` and the `proto` must be `udp`, so the record will look like this:
Copy link
Contributor

@pljones pljones Jan 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so the record will look like this

I'm not sure using jamulus.example.com as the host is great. Maybe service myserver.example.com and host host.example.com, allowing connection to myserver.example.com without the port being needed and that the Jamulus Server is running on host.example.com - to make it really clear.

_jamulus._udp.myserver.example.com. 60 IN SRV 0 5 12345 host.example.com.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Triage

Development

Successfully merging this pull request may close these issues.

2 participants