I put this in a feedback earlier, now posting here as a feature request:
Allow a user to have their own cname.domain.tld as the pointer for ARC to talk to the roon core. Currently you only allow a custom port number (and, roon does not allow port 443)
typical scenario:
- router / firewall locked down to only port 443
- router / firewall’s reverse proxy will inspect 443 traffic and look at ssl domain, then route/port forward or reject if just some arbitrary request on port 443 [standard stuff]
example of feature:
-
on my phone I have ARC, and in the settings to talk to my RoonCore at my home, I typed:
myarc.patricksdomain.net and it uses port 443 [today, the app only lets me set port] -
of course, the ‘internet’ knows to route myarc.patricksdomain.net to my local IP [the address Roon/ARC read and expose] - in home use, this is done via DDNS but I digress
*internally, I my router/firewall makes easy work of routing the 443 traffic from myarc.patricksdomain.net to my roon server (on any port required by the roon server for arc) -
unless I am missing something, this seems so much more scalable and supportable for the end users. and it does NOT preclude the current method of Roon harvesting the internet IP directly and requiring a port forward, it just allows another cleaner and slightly more secure option.
kind regards,
Patrick