# Selecting NIC ip address for ignition gateway

**URL:** <https://forum.inductiveautomation.com/t/selecting-nic-ip-address-for-ignition-gateway/78539>\
**Category:** Ignition\
**Created:** [August 30, 2023, 1:01am UTC](https://forum.inductiveautomation.com/t/selecting-nic-ip-address-for-ignition-gateway/78539 "2023-08-30T01:01:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![GaryL](https://avatars.discourse-cdn.com/v4/letter/g/bbe5ce/32.png) [@GaryL](https://forum.inductiveautomation.com/u/GaryL)\
**Post date:** [August 30, 2023, 1:01am UTC](https://forum.inductiveautomation.com/t/selecting-nic-ip-address-for-ignition-gateway/78539/1 "2023-08-30T01:01:23Z")

</div>

Hi all,

I recently ran into an issue where the clients machine had multiple NIC's with different ip addresses. One NIC was reserved for the IO/PLC/OPCUA network, and the other network was a line that went to the local network and eventually the (heavily firewalled) internet.

The question i have is while we were setting this machine up the gateway was automatically pointing to the NIC with the internet connection, i did not see anywhere to set the actual gateway NIC i wanted to use other than just the port. The correct NIC to use was the one without internet connection however it defaulted to the one with internet connection.

The only way we got it to switch over was to disable the line with the internet connection and restart the ignition service, it then selected the only available NIC.

Do you have any suggestions for 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:** [August 30, 2023, 1:20am UTC](https://forum.inductiveautomation.com/t/selecting-nic-ip-address-for-ignition-gateway/78539/2 "2023-08-30T01:20:38Z")

</div>

Don't use IP addresses. Use DNS names. Arrange for DNS to resolve to the production network for clients on that side of the Ignition gateway, and to resolve to the internet connection's IP address for that side. Put the DNS name into the public HTTP address setting on the gateway.

Ignition itself generally lets the machine's OS select what NIC really gets used for any particular traffic. (There are overrides in some device drivers for special cases.)

Related topic:

> [@Failover not working, V8](https://forum.inductiveautomation.com/t/failover-not-working-v8/78511/5):
>
> 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. …