Alcatel-Lucent VitalQIP Technology White Paper page 22

contain the A records of those systems that are not DHCP clients. Of these, the Enter-
prise server itself, and any DNS/DHCP remote servers or Domain Controllers managed
by VitalQIP, need to be defined in VitalQIP as static IP objects of type "Server". Router
IP addresses need to be defined in VitalQIP as Static objects of class "Router" for DHCP
to work correctly. IP addresses of systems that are neither DHCP clients nor Windows
2003, for example UNIX-based servers, would also need to be defined in VitalQIP as
static objects with an appropriate class.
VitalQIP 6.1 SP1 cannot send static DDNS updates to MS-DNS using secure zones.
Therefore, in Solution 2 for now, you should have the global policy Static DDNS Update
set to False, and instead you need to perform DNS Generation periodically to get the
changes in static IP objects out to DNS. (Solution 4 discusses how this changes in Vi-
talQIP 6.2, which is able to send DDNS updates to MS-DNS secure zones.). The flow of
static IP updates is shown in Figure 6.
19
Alcatel-Lucent | Integration of VitalQIP® with Microsoft Windows 2003 Networking/Active Directory