If DHCP servers are available on the network and DHCP is enabled on the Metasys system devices, a DHCP server can automatically assign the addresses of the DNS servers to some devices. Alternatively, the DNS server addresses may be manually assigned. See Table 1 for specifics for each device.
If the network does not support DNS, then the host's file or registry entries of the Site Director must be updated with the host name/IP address pairs for all engines/servers on the Metasys site, and each child device (non-Site Director engine/server) must be updated with the host name/IP address pair of the Site Director (and any other Ethernet-based device with which it communicates).
Either DNS or local host file updates are necessary for successful communication between a Site Director and all devices on the Metasys site.
We recommend using DNS scavenging to ensure that old host records are cleaned up properly. The recommended scavenging interval is the same interval as the DHCP lease time.
For information on configuring DHCP and DNS on an engine, refer to the commissioning guide for your network engine:
- SNE Commissioning Guide (LIT-12013295)
- SNC Commissioning Guide (LIT-12013352)
- NAE85 Commissioning Guide (LIT-12011044)
- NIEx9 Commissioning Guide (LIT-12011922)
- LCS85 Commissioning Guide (LIT-12011568)
For information on configuring DHCP and DNS for a Metasys server, refer to Microsoft® Windows operating system literature. Also refer to the TEC Series Wireless Thermostat Controller System Technical Bulletin (LIT-12011414) and WRS Series Many-to-One Wireless Room Temperature Sensing System Technical Bulletin (LIT-12011095) for DHCP and DNS information on those respective devices.