Table of Contents
Advertisement
Alcatel-Lucent | Integration of VitalQIP® with Microsoft Windows 2003 Networking/Active Directory
Getting data from VitalQIP into Alcatel-Lucent DNS
VitalQIP 6.1 SP1 cannot perform DDNS updates to Secure Zones on MS-DNS, but it
can perform DDNS updates to secure zones on Alcatel-Lucent DNS. These can come
from the DNS Update Service, the VitalQIP client GUIs, CLI commands, or the VitalQIP
web client. Each would require the appropriate configuration, as described in the Admin-
istrator Reference Manual. They do not necessarily need to be Windows 2003 systems,
but the KDC needs to be a Windows 2003 DC.
Performing DNS Generation
Because almost all data can be put into Alcatel-Lucent DNS via DDNS updates, DNS
Generation should seldom be necessary. DNS Generation should be performed for
cases such as:
Adding, deleting, or modifying domain profiles
•
New DNS servers
•
Changes on a Resource Records tab in the VitalQIP GUI
•
In the Windows 2003 environment, DNS Generation should be performed as seldom as
possible, because it can conflict with dynamic updates being executed at the same time.
Getting MS-DHCP client hostnames into DNS
MS-DHCP can send secure DDNS updates directly to Alcatel-Lucent DNS, just as it
does to MS-DNS in Solution 2. It would be advantageous, however, for the DNS up-
dates to be performed after the Enterprise server has checked the names for duplicates
and renamed DHCP hosts to avoid duplicates. MS-DHCP would have the DNSConfig
options set so that it does not send dynamic updates. Instead, the VitalQIP MSDHCP
Monitoring Service sends the DHCP lease information to the QIP Update Service (via
the Message Service), the QIP Update Service checks for duplicates, and then forwards
the corrected names to the DNS Update Service, which can send secure DDNS updates
to Alcatel-Lucent DNS. The flow of DHCP Client updates is shown in Figure 8.
27
Advertisement
Table of Contents
