# Selecting NIC ip address for ignition gateway **URL:** \ **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:** 1\ **Showing post:** 2
**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")
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. … --- _[View the full topic](https://forum.inductiveautomation.com/t/selecting-nic-ip-address-for-ignition-gateway/78539)._