If you’re looking to set up multiple Orchestrators/Transcoders in different locations around the globe it may be worth setting geo locating DNS services to improve your latency score.
Best of all you can connect all the geo nodes to a single Orchestrator account and run them anywhere on earth.
Ie. All North America requests go to your Chicago node, all Europe requests go to your London node and all Asia requests go to your Singapore node, all using the same domain.
Here is a guide to help you set up geo-locating DNS using Route 53.
- Register/Login to Amazon and access the Route 53 | Homepage
- Register or transfer your domain into Route 53 | Register Domain
- Create a Hosted Zone with your domain name (public) | Hosted Zones
- Create a Traffic Policy | Traffic Policy
- Start point – A: IP address in IPv4 format
- Add “Geolocation rule” and select your desired region
- Click “Connect to…” and select “New endpoint”. Enter the destination IP.
NOTE: This IP must be located within the region selected, else Transcoders and Broadcasters will not be able to connect.
- Repeat this step by clicking “Add another geo location” until desired locations met
- Make sure to have one location set as “Default” pointing one of your IPs. Some requests come from outside any set region or mask their location, all these requests resolve to your default.
- Save the new Traffic Policy (you will be prompted to purchase the AWS service here, if you prefer, you can skip this step and come back to it later under the Policy Records tab)
- Create a new Policy Record, select the settings you just made.
- Recommend leaving the “Policy record DNS name” empty and adjust the “TTL” to 1.
A few configuration reminders. The service address or service URI for your Orchestrator must be published as XXXX.com:port. You cannot forward the port within the DNS.
Run each instance of your Orchestrator at each location all connecting to the same domain and port.
Test that the DNS is resolving correctly by connecting through a VPN within a specified region and ping or trace route the domain. It should resolve to the settings you have configured.
Or use https://www.whatsmydns.net/
Hope this helps,