# DNS and Gateway Redundancy

**URL:** <https://forum.inductiveautomation.com/t/dns-and-gateway-redundancy/87507>\
**Category:** Ignition\
**Tags:** redundancy\
**Created:** [March 18, 2024, 6:12pm UTC](https://forum.inductiveautomation.com/t/dns-and-gateway-redundancy/87507 "2024-03-18T18:12:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nick\_Gendron](https://avatars.discourse-cdn.com/v4/letter/n/bcef8e/32.png) [@Nick\_Gendron](https://forum.inductiveautomation.com/u/Nick_Gendron)\
**Post date:** [March 18, 2024, 6:12pm UTC](https://forum.inductiveautomation.com/t/dns-and-gateway-redundancy/87507/1 "2024-03-18T18:12:56Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [March 18, 2024, 6:50pm UTC](https://forum.inductiveautomation.com/t/dns-and-gateway-redundancy/87507/2 "2024-03-18T18:50:42Z")

</div>

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.