TargetR Stacks can be linked to custom domain names.
For example, a partner who owns the domain name mycompany.com can create the sub domain, signage.mycompany.com, and use this for accessing the platform. The domain name can be used for signing in to the admin interface and (optionally) used by screens to communicate with the TargetR Stacks platform.
To link a custom domain to the TargetR Stacks platform you must be able to modify the DNS configuration for the domain.
Linking a custom domain name
- Sign in to your DNS management service.
- Create a new CNAME record.
- Set the name to be the required subdomain, for example signage.
- Set the value to be stacks.targetr.net.
When correctly configured, the admin interface will be accessible by typing the new address into a web browser. For example: http://signage.mycompany.com.
When the domain is first linked, secure connections will be served using a self-signed certificate. This means the browser will display a warning. After 5 minutes, the system should have installed a certificate for the new domain provided by LetsEncrypt.
It is important that there are no DNS CAA records preventing this process.
DS Loader and player software uses digitally signed server responses (asymmetric cryptography). This does not require SSL to be enabled for the custom domain and also does not require a real-time, battery backed clock or reliable NTP service. This is for maximum performance and device compatibility.
CNAME at root of domain
We recommend creating a sub domain for the digital signage platform. This is because CNAMEs at the root level can cause problems, especially when using the domain for other purposes.
§3.6.2 of RFC 1034:
If a CNAME RR is present at a node, no other data should be present; this ensures that the data for a canonical name and its aliases cannot be different. This rule also insures that a cached CNAME can be used without checking with an authoritative server for other RR types.
Many DNS services will not let you create a CNAME at the root of the domain - only an A record (IP address). Our platform uses multiple IP addresses for a pool of servers that are selected by health checks and latency. Therefore, a CNAME is required to provide both redundancy and performance.