# Hostname resolution

**URL:** <https://forum.inductiveautomation.com/t/hostname-resolution/111698>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [October 24, 2025, 10:35am UTC](https://forum.inductiveautomation.com/t/hostname-resolution/111698 "2025-10-24T10:35:39Z")\
**Posts on this page:** 1\
**Showing post:** 5

<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:** [October 24, 2025, 11:17am UTC](https://forum.inductiveautomation.com/t/hostname-resolution/111698/5 "2025-10-24T11:17:37Z")

</div>

> [@jakned](#):
>
> since I have some application logic tied to a location

This is reason #1 to not use Perspective for fixed-location HMIs. The code you are trying to run (in Perspective) actually runs in the gateway, which won't have any insight into the client's route tables.

Vision can do this, and can interrogate more reliable unique info, like local MAC addresses.

> [@Mobile Client MAC Address](https://forum.inductiveautomation.com/t/mobile-client-mac-address/23037/10):
>
> In a real Vision client, you can obtain the local MAC addresses with the following script: from java.net import NetworkInterface # Get list of local mac address as strings def myMacIds(): macs = [ni.hardwareAddress for ni in NetworkInterface.getNetworkInterfaces() if ni.hardwareAddress] return [":".join(["%02x" % (b & 0xff) for b in mac]) for mac in macs] Also, again in a real Vision client, you can obtain the outbound network interface and the corresponding local IP address the clien…

---

_[View the full topic](https://forum.inductiveautomation.com/t/hostname-resolution/111698)._