# Bind to multiple interfaces for redundancy failover

**URL:** <https://forum.inductiveautomation.com/t/bind-to-multiple-interfaces-for-redundancy-failover/97623>\
**Category:** Ignition\
**Tags:** redundancy\
**Created:** [October 22, 2024, 4:28pm UTC](https://forum.inductiveautomation.com/t/bind-to-multiple-interfaces-for-redundancy-failover/97623 "2024-10-22T16:28:12Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [October 22, 2024, 4:36pm UTC](https://forum.inductiveautomation.com/t/bind-to-multiple-interfaces-for-redundancy-failover/97623/3 "2024-10-22T16:36:47Z")

</div>

This is the key requirement:

> [@Architecture for Distributed Control Center](https://forum.inductiveautomation.com/t/architecture-for-distributed-control-center/85104/9):
>
> any loss of comms also results in loss of comms to all clients and all devices and all databases

Also, all clients should target main and backup servers via DNS name, not IP address, and the gateways should be publicly advertising their DNS names.

---

_[View the full topic](https://forum.inductiveautomation.com/t/bind-to-multiple-interfaces-for-redundancy-failover/97623)._