Solution 1: Adding Windows 2003 Support To An Existing Vitalqip; Installation: An All-Alcatel-Lucent Solution - Alcatel-Lucent VitalQIP Technology White Paper

Solution 1: Adding Windows 2003 support to an existing VitalQIP

installation: an all-Alcatel-Lucent solution

Alcatel-Lucent | Integration of VitalQIP® with Microsoft Windows 2003 Networking/Active Directory
Design overview
If Windows 2003 networking is being added to an existing VitalQIP installation, a primary
concern is how to get the SRV records into DNS and then into the VitalQIP database.
The Windows 2003 clients need to be able to locate network services by performing
queries of SRV records in DNS, and resolving those server hostnames to IP addresses.
Adding these records in the traditional way (entering them into the VitalQIP GUI and
performing DNS Generation) is difficult to do in a timely manner. Instead, the Domain
Controllers should be added to the Access Control List of the appropriate domains in
Alcatel-Lucent DNS so that they can add or delete the necessary records dynamically.
Alcatel-Lucent DNS, in turn, can use External Updates to put this information into the
VitalQIP database.
If Alcatel-Lucent DHCP is being used already, it would be best to keep the existing mes-
sage routes and methods, and let Alcatel-Lucent DHCP and the Enterprise server put
the DHCP hostname into DNS, not the clients themselves. In brief, the DHCP clients
register their hostnames with Alcatel-Lucent DHCP, which generates messages for the
VitalQIP Message Service. The VitalQIP Message Service sends those messages to the
VitalQIP QIP Update Service, which validates the hostnames and passes the data to the
VitalQIP DNS Update Service. The VitalQIP DNS Update Service sends DDNS Updates
to the DNS servers, as shown in the message flow diagram in Figure 1.
5