+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: General Questions (https://forum.jellyfin.org/f-general-questions)
+--- Thread: What are the service names and TXT data used in Jellyfin's Service Discovery? (/t-what-are-the-service-names-and-txt-data-used-in-jellyfin-s-service-discovery)
What are the service names and TXT data used in Jellyfin's Service Discovery? - senseivita - 2024-02-23
I have a Jellyfin instance in another network behind a proxy, I'd like to make it available on every, or most, subnets using permanent DNS-SD (unicast), but I don't know what records or rather, service names it uses, nor their properties, e.g;
Plan
I'll translate the multicast DNS to centralized unicast DNS by delegating that part of it to a macOS High Sierra Server Mac (from Active Directory) specific for that task. Since it's just regular DNS in a very static configuration, I'd like to have a subset of permanent records, like Jellyfin.
I've done it before, it's very cool I think. Eliminates the need to forward multicast traffic, to flood UDP across subnets, works with VRRP, doesn't make hosts to change their name adding a number in parenthesis after thinking they've been duped like Avahi does, and uses existing DNS servers and thus are subject to DNS policies. Any DNS server could be used I know, but macOS comes with dnsextd for DNS-LLQ and DNS-UL.
I dumped* some services scanning the network specifically for them it but there are thousands of lines in a one-minute scan and that's not even all the service names I know that could be present. :(
If you guys could help me out with the spec, preferably in a "for dummies" context (though I'm thankful either way), that would be awesome.
Thanks!
*: dns-sd -Z delivers an almost ready-to-use BIND9 zone file, run it in parallel in a bash script, redirect it output, self-kill a minute later, and that's it.
_
RE: What are the service names and TXT data used in Jellyfin's Service Discovery? - sevenrats - 2024-02-23
i can tell you right now nobody understands this question at all. reflecting mdns across different subnets is not something we support, since its more "extreme networking edge case" than "media server feature."
in particular, this solution is so much more cumbersome than a DHCP reservation I can't even wrap my head around it. Use a DHCP reservation for your jellyfin server and you solved this problem all at once.