# OPC connection displays tags from the wrong OPC server **URL:** \ **Category:** Ignition\ **Tags:** opcua\ **Created:** [February 3, 2026, 1:53pm UTC](https://forum.inductiveautomation.com/t/opc-connection-displays-tags-from-the-wrong-opc-server/113722 "2026-02-03T13:53:51Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Andrea\_Salmaso](https://avatars.discourse-cdn.com/v4/letter/a/4da419/32.png) [@Andrea\_Salmaso](https://forum.inductiveautomation.com/u/Andrea_Salmaso)\ **Post date:** [February 3, 2026, 1:53pm UTC](https://forum.inductiveautomation.com/t/opc-connection-displays-tags-from-the-wrong-opc-server/113722/1 "2026-02-03T13:53:51Z")
Hi, I recently came across a really strange issue with one of my OPC connections (MACHINE01, fantasy name). The OPC server endpoint is > opc.tcp://MACHINE01:4840 At some point, when browsing the tags of this connection from the Designer, I wasn’t seeing MACHINE01 tags anymore. Instead, I was actually seeing the ones from another OPC server I had connected (MACHINE02). > opc.tcp://MACHINE02:4840/AxesBrainOPC\_UA As a consequence, all the tags from MACHINE01 that I had previously imported were giving me a “_ **Bad\_NodeIdUnknown** _“ error. The first thing I did was create a new connection in UAExpert for that OPC server, and everything looked fine: I could see MACHINE01's tags as expected. So I assumed the OPC server itself was working correctly. To fix it, I opened the OPC connection configuration page in the Gateway: > Config \> Opc \> OPC Connection \> MACHINE01 \> More \> endpoint Then I clicked _Next_ through the wizard until the end, and finally clicked _Save Changes_. After doing this, everything went back to normal. All of these devices work with DHCP, without reservations, and they have an 8‑hour lease time, so their IP addresses can of course change during the day/week. One hypothesis I came up with is that Ignition might keep some internal cache of the IP addresses resolved from hostnames, and that this cache may become out of sync with the real IPs. Another possibility is that we might be resolving the hostname incorrectly. Does anyone have an idea of what could have happened? Thanks! ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [February 3, 2026, 2:24pm UTC](https://forum.inductiveautomation.com/t/opc-connection-displays-tags-from-the-wrong-opc-server/113722/2 "2026-02-03T14:24:08Z")
> [@Andrea\_Salmaso](#): > > All of these devices work with DHCP, without reservations, and they have an 8‑hour lease time, so their IP addresses can of course change during the day/week. Insanity ---
**Author:** ![Andrea\_Salmaso](https://avatars.discourse-cdn.com/v4/letter/a/4da419/32.png) [@Andrea\_Salmaso](https://forum.inductiveautomation.com/u/Andrea_Salmaso)\ **Post date:** [February 3, 2026, 2:35pm UTC](https://forum.inductiveautomation.com/t/opc-connection-displays-tags-from-the-wrong-opc-server/113722/3 "2026-02-03T14:35:57Z")
Thanks Kevin. I’m aware it’s not ideal — this setup is inherited. Still, I’m trying to understand whether DHCP alone could explain the behavior I saw, or if Ignition might have cached an old DNS resolution. If you have any insight on that part, it would be super helpful. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [February 3, 2026, 2:39pm UTC](https://forum.inductiveautomation.com/t/opc-connection-displays-tags-from-the-wrong-opc-server/113722/4 "2026-02-03T14:39:45Z")
Yes, I think there's multiple places in the stack where this DNS resolution could get cached with varying expiration times. Your OS, the network infrastructure providing DNS, Java... I do think that Ignition's OPC UA connection configuration should probably include the server URI, at least optionally and automatically filled in when the server is configured via online discovery, and use that to make sure the server can't get changed out from underneath it like this when all other settings are equivalent. That would just leave you with a faulted connection until it was reset, but that's better than a connection to the wrong server. ---
**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:** [February 3, 2026, 2:52pm UTC](https://forum.inductiveautomation.com/t/opc-connection-displays-tags-from-the-wrong-opc-server/113722/5 "2026-02-03T14:52:18Z")
> [@Kevin.Herron](#): > > Insanity 💯 Oy!