Table of Contents
Advertisement
VitalQIP Product Description
Features
While VitalQIP will not store the Active Directory access control information, it will require the user to
create two new Windows 2000 users for QIP. One will be a normal user, referred to as a Strong user. The
other will be a member of the DNSUpdateProxy security group, referred to as a Proxy user.
When static objects and RRs are modified in a secure zone, VitalQIP will use the Strong user context to
do the update. This will cause VitalQIP to be the only user that is allowed to modify those entries, thus
locking out random clients from stealing DNS entries that were entered by VitalQIP. When EDUP
objects and RRs are updated, the Proxy user context will be used, thus allowing external users to make
modifications (and take ownership of) those entries.
When dynamic objects are updated, the user may possibly want to allow the DHCP client to take
ownership of the name and make subsequent updates to DNS itself. In this case, QIP will use the Proxy
user context. On the other hand, users may feel more comfortable with VitalQIP managing the DNS
updates for the dynamic clients and not allowing the dynamic clients to update the zone at all. In this case
QIP will use the Strong user context to do the updates, thus locking any other users out of being able to
modify the information.
3.27 Changed Records Push
VitalQIP provides an option to execute pushes of changed records only to Active Directory DNS reducing
tombstoned records. Pushing only changed records significantly reduces replication traffic between
domain controllers, and allows clients to maintain ownership of resource records they have placed in
DNS. This option will only be provided when a Windows 2000 DNS server type is selected.
3.28 Secure Messaging
VitalQIP can dynamically update secure MS DNS Zones. In addition, all DNS and DHCP Push Requests
and DHCP Lease traffic can be secured by configuring SSL within the VitalQIP product. This also offers
"Real World" encryption for database login information. A ll communication packets between servers can
be encrypted, ensuring security within your organization.
3.29 DNS & DHCP Server Compatibility
The Lucent DHCP Server can update both primary and secondary DNS servers with resource record
information as DHCP leases are granted and deleted. The Lucent DNS Server fully supports Incremental
Zone File Transfer, RFC 1995 (IXFR), across UNIX and Windows platforms.
The Lucent DHCP Server supports a many-to-one hot fail-over to another DHCP server in the event of
server outage. This feature provides the high availability and reliability required for IP address services.
3.30 DNS – Domain Name Server and Dynamic DNS
Alcatel-Lucent Technologies has taken an open, non-proprietary approach to DNS management. Alcatel-
Lucent's focus is on integrating and supporting the latest commercial releases of Internet Software
Consortium - BIND (ISC BIND) code across multiple platforms. All DNS communications and
configurations are standards based.
Alcatel-Lucent's approach offers the customer a number of advantages:
©
Copyright
2009 Alcatel-Lucent
Page 36
Use pursuant to company instructions
Hide quick links:
Advertisement
Table of Contents
