Updates Running-a-server.md to cover DNS SRV support#874
Updates Running-a-server.md to cover DNS SRV support#874ginjo wants to merge 27 commits intojamulussoftware:next-releasefrom
Conversation
Adding documentation for DNS SRV record support
Adding DNS SRV support documentation
Adding DNS SRV support documentation
Adding DNS SRV support documentation
| #### Creating SRV records | ||
|
|
||
| SRV records are created by the administrator of the domain being used to host the Jamulus server. The SRV records are added through the administration portal (or API if available) of the domain's DNS hosting service. The format of the SRV record entry can vary by DNS hosting service but will generally look something like this. | ||
|
|
There was a problem hiding this comment.
I think this section should also describe how hosting multiple Jamulus Servers on a single system would work, giving each its own "simple name".
|
Thanks @mcfnord , I like the improvements. @pljones , regarding further description of the one-host-to-many-servers that you mentioned... Maybe something like this? Example use case with SRV recordsAssuming DNS CNAME or A record resolves server1.mydomain.com, and server1.mydomain.com has three Jamulus server instances each listening on one of the three specified ports. Alternatively, server1.mydomain.com can be a router, NAT-gateway, or load-balancer that forwards each of the ports to a backend Jamulus server (or servers). It's important to remember that DNS is not forwarding connections. It's simply telling Jamulus client what public host:port to connect to. |
Looks useful to have, great! Formatting may need some improvement... Maybe use a table..? (Or not...)
|
Yes, I think the table looks better. The squashed SRV entries are less readable, but the absence of horizontal scrolling is a big improvement: Example use case with SRV recordsAssuming DNS CNAME or A record resolves server1.mydomain.com, and server1.mydomain.com has three Jamulus server instances each listening on one of the three specified ports. Alternatively, server1.mydomain.com can be a router, NAT-gateway, or load-balancer that forwards each of the ports to a backend Jamulus server (or servers).
It's important to remember that DNS is not forwarding connections. It's simply telling Jamulus client what public host:port to connect to. |
Co-authored-by: John Dempsey <[email protected]>
Co-authored-by: John Dempsey <[email protected]>
Co-authored-by: John Dempsey <[email protected]>
Co-authored-by: John Dempsey <[email protected]>
Co-authored-by: John Dempsey <[email protected]>
|
FYI I broke out "Running an Unregistered Server" into a separate page in #875 so can put the changes in this PR into that once this one is done (there's probably some clever git way of doing it but I'll just copy/paste) |
Co-authored-by: John Dempsey <[email protected]>
Co-authored-by: Peter L Jones <[email protected]>
Removed mydomain.com. Grammar improvements.
Minor improvements to wording. Co-authored-by: John Dempsey <[email protected]>
wiki/en/Running-a-Server.md
Outdated
|
|
||
| #### Example use case with SRV records | ||
|
|
||
| This example assumes a DNS A or CNAME record resolves ```server1.example.com```, and ```server1.example.com``` has three Jamulus server instances, each listening on one of the three specified ports below. |
There was a problem hiding this comment.
I think this should be rephrased as the grammar seems strange (I'm not a native speaker.)
Updates SRV record section. Co-authored-by: ann0see <[email protected]>
Updates SRV record section. Co-authored-by: ann0see <[email protected]>
Updates SRV record section. Co-authored-by: ann0see <[email protected]>
Updates SRV record section. Co-authored-by: ann0see <[email protected]>
Updates SRV record section. Co-authored-by: John Dempsey <[email protected]>
Updates SRV record section. Co-authored-by: ann0see <[email protected]>
Updates SRV record section. Co-authored-by: ann0see <[email protected]>
Updates SRV record section, changing client to Client
I'm fine with it - but I don't know what this comment from @pljones implies (I'm not close enough to the details) https://github.com/jamulussoftware/jamuluswebsite/pull/874/files#r1026094826 |
Co-authored-by: ann0see <[email protected]>
|
Ah, conflicts. But since this PR was raised, we now have a seprate page in which to put these docs (Unregistered-Servers.md - at least I assume its only relevant to that). If so, how best to proceed? Shall I just take the current content and raise another PR with it in? |
Adjusts wording in SRV record section Co-authored-by: John Dempsey <[email protected]>
Adjusts wording in SRV record section Co-authored-by: John Dempsey <[email protected]>
Co-authored-by: John Dempsey <[email protected]>
|
Replacing with #904 to resolve issues. |
Short description of changes
Add documentation to Running-a-server.md to cover new DNS SRV support feature.
Context: Fixes an issue? Related issues
jamulussoftware/jamulus#2930
Status of this Pull Request
Review needed
What is missing until this pull request can be merged?
Merged but needs documentation
Does this need translation?
Yes
Checklist