DNS and Name Resolution

Reliable name resolution is an important part of ensuring stable communication between visability system components. If DNS is in use within your environment, it must be properly configured and functioning prior to commissioning.

While vis|ability can operate using IP addresses alone, consistent and accurate name resolution simplifies system management and reduces the risk of connectivity issues.

In a vis|ability deployment, multiple systems must communicate with one another consistently — including the System Manager (ASM), Display Nodes, and client interfaces.

When DNS is properly configured:

• Systems can be accessed using hostnames instead of IP addresses
• Device identification becomes easier for both IT teams and deployment engineers
• Configuration is more resilient to changes in underlying infrastructure

If DNS is misconfigured or unreliable, it can lead to intermittent connectivity issues that are difficult to diagnose.

If your environment utilizes DNS, the following should be confirmed prior to commissioning:

• DNS services are operational and reachable from all visability systems
• All visability-related devices have valid DNS entries (A records)
• Hostnames resolve correctly to their assigned IP addresses
• Forward and reverse lookups (if applicable) are consistent

Before deployment, perform basic validation from each system:

• Verify that all visability components can:
  • Resolve the hostname of the System Manager
  • Resolve the hostnames of other relevant systems
• Confirm that:
  • Hostnames return the correct IP address
  • No duplicate or conflicting DNS entries exist

These checks help ensure that systems can reliably locate and communicate with one another.

In environments where DNS is not available or not used, visability can still operate using static IP addressing.

In these cases:

• IP addresses must be clearly documented in the network schema
• Any required host mappings should be configured consistently (e.g., local host files)
• Care should be taken to avoid discrepancies between systems

• Missing or incorrect DNS records
• Hostnames resolving to outdated or incorrect IP addresses
• Inconsistent name resolution across different VLANs or network segments
• Reliance on DNS without proper validation