# Failover not working, V8

**URL:** <https://forum.inductiveautomation.com/t/failover-not-working-v8/78511>\
**Category:** Ignition\
**Created:** [August 29, 2023, 1:57pm UTC](https://forum.inductiveautomation.com/t/failover-not-working-v8/78511 "2023-08-29T13:57:39Z")\
**Posts on this page:** 1\
**Showing post:** 5

<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:** [August 29, 2023, 2:18pm UTC](https://forum.inductiveautomation.com/t/failover-not-working-v8/78511/5 "2023-08-29T14:18:49Z")

</div>

> [@twilliams](#):
>
> Both servers are running dual NICs

While highly desirable for many applications, this plays havoc with redundancy if Ignition clients can connect through either network.

The only good solution I'm aware of is to have DNS on all networks resolve names for these gateways, in such a way that the IP returned for your gateway to a client is the correct address **for that client's network**.

Then the Public HTTP Address setting that Kevin points out can be set to the domain name and all of your clients will "just work" using that name.

{FWIW, the setting in `dnsmasq` for the desired response behavior is called "localize queries".}

---

_[View the full topic](https://forum.inductiveautomation.com/t/failover-not-working-v8/78511)._