# Keeping TestGateway in Synch with Production Gateway - TestbedPLC vs. Real PLC

**URL:** <https://forum.inductiveautomation.com/t/keeping-testgateway-in-synch-with-production-gateway-testbedplc-vs-real-plc/110850>\
**Category:** Ignition\
**Tags:** opcua, ignition81\
**Created:** [September 22, 2025, 8:27pm UTC](https://forum.inductiveautomation.com/t/keeping-testgateway-in-synch-with-production-gateway-testbedplc-vs-real-plc/110850 "2025-09-22T20:27:49Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [September 22, 2025, 8:30pm UTC](https://forum.inductiveautomation.com/t/keeping-testgateway-in-synch-with-production-gateway-testbedplc-vs-real-plc/110850/2 "2025-09-22T20:30:11Z")

</div>

In 8.1, the clean solution is to set up local DNS names for your PLCs, and use those names in your gateways. Then the local `/etc/hosts` file (or equivalent infrastructure) would point to the correct IP addresses for that gateway's role. (And for DB connections and other peer systems.)

(Better options in v8.3 deployment modes.)

---

_[View the full topic](https://forum.inductiveautomation.com/t/keeping-testgateway-in-synch-with-production-gateway-testbedplc-vs-real-plc/110850)._