When entering machine names during installation and configuration, you must enter either the fully qualified DNS domain name (FQDN) or a static IP address.
A fully qualified domain name specifies a computer's exact location within the tree hierarchy of the Domain Name System (DNS). For example, the FQDN myhost.mycompany.com uniquely distinguishes the device from any other hosts called "myhost" in other domains. Be sure to enter the FQDN in lowercase.
Static IP Address
Static IP addresses are manually assigned to a computer and are guaranteed not to change (unless changed by the administrator). Dynamic addresses may stay the same for long periods but are subject to change. When the IP address changes (often without warning), the SSL certificate will no longer be valid; therefore, dynamic IP addresses should not be used.
Maximum Length of Machine Names
The machine name must be 15 characters or less. Machine names of more than 15 characters are not supported at this time. For example, if installing to mymachinename.mycompany.com, the "mymachinename" segment is 13 characters and is supported. If you tried to install to "mylongmachinename.mycompany.com", the segment is 17 characters and not supported.
FQDN Requirement for Workgroups
Windows computers can be networked together in Domains and Workgroups.
- Domains are used for large scale deployments with dozens of computers connected to the network. The FQDN for a domain is in the format myhost.mydomain.com.
- Workgroups are typically used when there are only a few computers connected to the network. The FQDN for a workgroup computer combines the Host Name and Primary DNS Suffix. For a PC with a host name of PCJOE and Primary DNS Suffix of "local", the FQDN would be PCJOE.local. You can find out the Host Name and Primary DNS Suffix by opening cmd.exe and typing ipconfig /all.
Special Note about "Unmanaged" Networks and FQDNs
Issues can result when operating Prism in an "unmanaged" network and using Fully Qualified Domain Names (FQDNs). An unmanaged network is one that does not manage the distribution and resolution of IP Addresses through the standard tools Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS). In a standard network, each machine is automatically assigned a network address by the DHCP server. In addition to a network address, the DHCP server tells each machine about one or more DNS servers that can be reached to resolve domain names.
In an unmanaged environment, IP addresses are statically configured. The machines do not receive an IP address from DHCP and thus do not learn about any DNS servers. This becomes a problem if using FQDNs when installing Prism or configuring replication. Without DNS, there will be no way for the network to resolve the FQDN to a valid IPV4 or IPV6 address.
When using Prism in an unmanaged network with FQDNs, you have two options:
1. Reconfigure the network to use a DNS server.
2. Edit the hosts file on each machine (C:\Windows\System32\Drivers\etc). This option has two major drawbacks. First, it creates an administrative burden. Second, iOS does not use a hosts file so this option is only available for Windows OS.