VitalQIP Product Description
What’s New in VitalQIP 7.2
VitalQIP configures zones for DNS Views through one of these methods:
•
Sharing existing global zone data into a DNS View. Any subsequent changes made to the data
in the global zone, except the SOA MNAME and NS records, comprise the zone data in the
DNS View.
•
Defining a zone with contents specific to a DNS View. All new data specified through Object
FQDNs and View-specific Node Domain Names in addition to new SOA, and NS records
comprise the zone data in the DNS View.
Both methods allow DNS to provide different access or restrictions. Only view specific zones can provide
clients with answers that are different from the global namespace.
There are many scenarios in which a customer may choose to use BIND Views, the following are a few
examples:
•
Customers that use DNS Views to have the DNS server responded differently depending on
where the request was located geographically. In this case, customers use geographically-
oriented Access Control Lists (ACLs), and then use DNS Views to direct a client in a particular
area to the closest gateway or server for that area.
•
Another use case is the situation where a name server can provide different responses to queries
from internal hosts in an organization’s intranet and external hosts in the Internet. Thereby
responded differently to internal and external requests.
7.3
Report Enhancements
In the VitalQIP 7.x release incorporated a new reporting package called Jasper Reports. This allows both
patch and major releases to incorporate more and more reports to better server our overall customer base
and needs. In this release, in addition to new reports, the report hierarchy has been reorganized so that
reports for a specific feature can be collapsed or hidden altogether.
Enhanced reports available in 7.2:
•
Audit Reports have been added for Subnet Organization, Network, Organization, DNS View,
and Managed Files
•
ACL Template Usage Reports: List all the Views, Zones, ACLs etc., in which the specified
ACL Template is in use. An administrator would use this information before the deletion of an
ACL.
•
Report on Objects by Address Range
•
Resource Record Report permits Resource Records to be searched by Type of RR (A, PTR,
CNAME, MX, and so on), and the level at which it exists (All, Domain, Reverse Zone, and
Object)
•
Report Generation from Search Results for a Node, an IPv4 Object, or Resource Records
•
Object by Administrator Report
•
Resource Records by Zone and View Specific Zone Report
•
View Specific Zone Reports supports DNS Views Resource Records
•
Audit Reports for Admin Roles and Managed Lists
Copyright
©
2009 Alcatel-Lucent
Page 50
Use pursuant to company instructions
