Table of Contents
Advertisement
VitalQIP Product Description
•
Because of VitalQIP software's unique design and open approach, companies can choose to
deploy any vendor's BIND-compliant DNS server. The software can be used to manage these
DNS servers in much the same way as it manages its own DNS Server
•
Alcatel-Lucent allows customers to deploy and manage Alcatel-Lucent DNS services on either
standard base servers or the Alcatel-Lucent Appliances. By supporting heterogeneous
deployments, customers can protect their investment and have the flexibility to deploy on their
platforms of choice
•
VitalQIP software currently supports both BIND 8 and 9 on servers as well as the Alcatel-
Lucent Appliances. By concurrently supporting multiple releases of BIND, the software allows
customers to have an orderly migration to new releases
•
Alcatel-Lucent enhances the ISC BIND code, as needed, with coding extensions to accelerate
adoption of key RFCs demanded by the market. As updated versions of BIND become
available, Alcatel-Lucent Technologies adopts the new ISC BIND and extends it with any
critical features not yet incorporated.
DNS zone and data configurations are performed through the VitalQIP client and stored in the enterprise
database. Configuration attributes include:
•
Domain Name
•
Scheduled update intervals (for serial number increments)
•
Zone directory
•
Zone e-mail
•
BIND Version (selective to server – 8.x, 9.x, and MS 4.0, Windows)
•
Additional Start of Authority Record (SOA) attributes (information about the zone: refresh,
retry, expire)
•
Most common BIND 8.x and 9.x directives (notify, also-notify, allow updates
•
Secondary servers and secondary BIND versions
•
Corporate extensions – allow for additional directives/statements to be included in named.boot
and named.conf files
•
Domain extensions – provide the ability to include data files not managed by VitalQIP software.
3.31 Configuring Remote DNS Servers
Once the initial domain information is configured, VitalQIP software will generate all files necessary to
boot on the remote DNS server (named.conf, named.local, root.zone, named.root, and all zone data files).
This process is accomplished via the software, and the qip-rmtd (remote service) processes running on
remote machines. In the event that a primary server crashes or loses its data, this process quickly allows
administrators to reconfigure a new primary server in a matter of minutes.
VitalQIP software initiates a TCP connection to the remote server via a specific port number. The remote
process (qip-rmtd) then initiates a transfer of its configuration files from the database. This data is then
saved to the local directory and a kill –HUP performed against the named process to reload the data.
Dynamic DNS is also configured to be on/off at this time (based on a configurable system policy).
©
Copyright
2009 Alcatel-Lucent
Use pursuant to company instructions
Features
Page 37
Hide quick links:
Advertisement
Table of Contents
