DHCP implementation considerations - Metasys - LIT-12011279 - General System Information - Metasys System - 10.1

Network and IT Guidance Technical Bulletin

Brand
Metasys
Product name
Metasys System
Document type
Technical Bulletin
Document number
LIT-12011279
Version
10.1
Revision date
2019-12-20
Language
English

For Metasys devices to function properly in a DHCP implementation, the DHCP servers must support dynamic DNS. The DHCP infrastructure must be configured to do the following:

  • The DHCP server must create an A record in the defined DNS domain upon handing a lease to a Metasys device. Optionally, you can configure the DHCP server to update the PTR (pointer) record of the Metasys DHCP-supported device in the reverse zone DNS domain.

  • The domain for DNS updates must be included in the DHCP server configuration. The Metasys DHCP-supported device does not specify the domain.

  • The Metasys Server and/or network engine and the Metasys DHCP-supported devices (TEC20-3C-2 Coordinators and WRS-RTN Many-to-One Receivers) all must be in the same DNS domain.

  • We recommend that the Metasys Server and/or network engine and the Metasys DHCP supported devices (TEC20-3C-2 Coordinators and WRS-RTN Many-to-One Receivers) be in a separate VLAN from all other devices at the Metasys site.

  • If the DNS server, Metasys Server, network engine, and/or Metasys DHCP supported devices (TEC20-3C-2 Coordinators and WRS-RTN Many-to-One Receivers) are in different networks (VLANs), ensure that routing is available between networks and that a proper router is passed in the DHCP lease.

  • If the DHCP server is not in the same VLAN as the Metasys devices, enable DHCP forwarding to the proper DHCP server on the VLANs on which the Metasys devices are located.