# Ignition Network Interface Binding

**URL:** <https://forum.inductiveautomation.com/t/ignition-network-interface-binding/44986>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [March 27, 2021, 6:14am UTC](https://forum.inductiveautomation.com/t/ignition-network-interface-binding/44986 "2021-03-27T06:14:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![yifan.jiang](https://avatars.discourse-cdn.com/v4/letter/y/e9bcb4/32.png) [@yifan.jiang](https://forum.inductiveautomation.com/u/yifan.jiang)\
**Post date:** [March 27, 2021, 6:14am UTC](https://forum.inductiveautomation.com/t/ignition-network-interface-binding/44986/1 "2021-03-27T06:14:06Z")

</div>

Hi All, I have some questions about the network interface binding in Ignition, especially around redundancy.  
So, Assume we have 4 subnets on the gateway, all subnets will have clients connects to the ignition gateway. There is a lot legacy reasons for this setup and we are currently stuck with it. Here is what my test results are:

1. If i use subnet 1 as gateway redundancy network communication, it seems none of the clients on subnet 2-4 would be able to connect to gateway anymore.
2. If i then turn off auto detect http address, and place all the subnet 1-4 in the address field, the redundancy on subnet 2-4 would not work, it will report redundant connection unknown.  
At the moment, i am using a work around where i don’t specify an ip address in the redundancy interface binding field, but use server name. Then I can use client’s host file to resolve it into the corresponding subnet. Do any one have similar situation and was there a better choice in gateway settings under this situation?  
Thanks

---

<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 27, 2021, 7:45pm UTC](https://forum.inductiveautomation.com/t/ignition-network-interface-binding/44986/2 "2021-03-27T19:45:43Z")

</div>

IIRC, using the server name with subnet-dependent name resolution is the right answer. It doesn’t have to be handled in a client’s hosts file, though. Non-amateur DNS servers listening on multiple subnets can deliver the correct behavior. (Eg. the `--localise-queries` option in `dnsmasq`)

---

<div class="post-metadata">

**Author:** ![yifan.jiang](https://avatars.discourse-cdn.com/v4/letter/y/e9bcb4/32.png) [@yifan.jiang](https://forum.inductiveautomation.com/u/yifan.jiang)\
**Post date:** [March 31, 2021, 11:58pm UTC](https://forum.inductiveautomation.com/t/ignition-network-interface-binding/44986/3 "2021-03-31T23:58:47Z")

</div>

Thanks pturmel, I have looked at the windows equivalent of dnsmasq, which seems to be maraDNS, I will see if i can get more resources to put a DNS or a pair of DNS into the environment.

---

<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:** [April 1, 2021, 12:54am UTC](https://forum.inductiveautomation.com/t/ignition-network-interface-binding/44986/4 "2021-04-01T00:54:48Z")

</div>

> [@yifan.jiang](#):
>
> windows equivalent

My condolences. /: