Servers registering to directories based on SRV DNS records

[rdica]

While SRV records for servers simplifies client configs, has there been any thought to providing SRV records for directory servers?
I could see it simplifying server configs by not having to specify a port based on a genre.

I suppose I could try spinning up more directory servers and test this myself...

[rdica]

After installing the jamulus_headless 3.12.0beta1 deb, setting up a directory server and client server, and configuring SRV record, it appears one cannot use the name in the SRV record as an argument for --directoryaddress.
Here's complete journalctl -u jamulus-server output:

Feb 01 13:32:45 daw9.dhcp.ldev systemd[1]: Started jamulus-server.service - Jamulus headless server.
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]: - Starting in server mode by default (due to compile time option)
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]: - server mode chosen
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]: - no GUI mode chosen
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]: - disconnect all clients on quit
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]: - selected port number: 22124

Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]: - register with directory at address: jamtest.ldev

Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]: - server info: jamtest.ldev;daw9;us
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]: - welcome message: jamtest.ldev
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]: - logging file name: /data/jamulus/logs/jamtest.ldev.log
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]: - using multithreading
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]: - starting with delay panning
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]: Using "192.168.17.126" as external IP.
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]: Using server info: name = "jamtest.ldev", city = "daw9", country/region = "us" (United States)
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]: Recording state not initialised
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]: multithreading enabled, setting thread count to 2
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  *** Jamulus, Version 3.12.0beta1
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  *** Internet Jam Session Software
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  *** Released under the GNU General Public License version 2 or later (GPLv2)
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  *** <https://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  ***
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  *** This program is free software; you can redistribute it and/or modify it under
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  *** the terms of the GNU General Public License as published by the Free Software
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  *** Foundation; either version 2 of the License, or (at your option) any later version.
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  *** There is NO WARRANTY, to the extent permitted by law.
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  ***
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  *** This app uses the following libraries, resources or code snippets:
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  ***
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  *** Qt cross-platform application framework 5.12.8 (build), 5.15.13 (runtime)
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  *** <https://www.qt.io>
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  ***
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  *** Opus Interactive Audio Codec
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  *** <https://www.opus-codec.org>
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  ***
Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]:  *** Copyright © 2005-2024 The Jamulus Development Team

Feb 01 13:32:45 daw9.dhcp.ldev jamulus[1880]: Server Registration Status update: Bad address

Note that last line :(

dig srv _jamulus._udp.jamtest.ldev

; <<>> DiG 9.18.28 <<>> srv _jamulus._udp.jamtest.ldev
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55224
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;_jamulus._udp.jamtest.ldev.	IN	SRV

;; ANSWER SECTION:
_jamulus._udp.jamtest.ldev. 0	IN	SRV	0 0 40124 daw9.dhcp.ldev.

;; Query time: 1 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Sat Feb 01 13:39:11 EST 2025
;; MSG SIZE  rcvd: 89

Doesn't appear to resolve SRV records, is that a client only function then?

[ann0see]

is that a client only function then?

Yes. I think so. You can have a look at the code for the SRV handling. I'm not sure how much we can do for directories. It's certainly an edge case.