DNS and Gateway Redundancy

Ignition
1

I'm managing two gateways set up for redundancy and looking for the most efficient way to manage DNS across both hosts.

I'm considering utilizing nginx as a reverse proxy to route traffic primarily to the first server, with an automatic switch to the backup server in case the first one fails. However, I'm curious if there's a built-in feature within the Ignition gateway that offers similar functionality.

The goal is for the hostname app.company.local to always point to the active node.

Has anyone faced a similar challenge with gateway redundancy and DNS management? How did you address it?

2

Don't hide the redundancy behind a proxy. Ignition's clients need to be able to target them directly. The Vision Client Launcher and Perspective Workstation allow you to specify both server URLs for their shortcuts/targets. Once running, Vision and Perspective fail over intelligently.