DNSv3
ProVision's DNSv3 combines server management, group organization, and zone management under the DNS tab.
The DNS tab contains four sub-tabs: DNS Groups, DNS Servers, DNS Zones, and DNS Records.
The DNS Groups tab is where DNS groups, zones, ACL's, and default SOA values are managed. The DNS tab Groups List allows you to create, view, and manage groups of DNS servers and zones. Using groups, you can configure and push selected combinations of zones at one time.
The DNS Servers tab is only accessible to Admin users, and contains functions for adding, updating, and managing DNS servers as well as scheduling server tasks. For Admin-level DNS tasks, see DNS Administration and Working with DNS Servers.
The DNS Zones tab lists all the zones able to be viewed by the user, in the same format as on the DNS Groups page, but without the group organization. The Zone List allows you to view, add, delete, and push individual DNS zones.
The DNS Records tab list all records viewable by the user, in a filterable list to expedite search, editing, and managing records. New records may also be added from this page.
DNSv3 Overview
DNSv3 organizes ProVision's DNS system into a more unified and accessible interface, combining both admin and non-admin DNS tasks together under the DNS tab.
In DNSv3, zones are gathered under DNS groups, servers are attached to those groups, and Nameservers, Default SOA values, and ACLs are managed at a per-group level. Users can then view and manage groups, individual zones, default SOA values, ACLs, attach servers, and perform pushes all on the same page.
DNS Permissions
DNSv3 incorporates DNS zones and groups into the Resource System. Zones and groups are resources just like Customers, Servers, Routers, or Contacts (See The Resource System for a more detailed explanation of resources in ProVision).
This allows for DNS zones and group permissions to be managed similarly to other resources, where users with resource permissions (Create / Read / Update / Delete) on the parent resource of the DNS group can create groups and zones, manage those groups and zones, push (if a server is attached), and delete.
A user with full resource permissions on a DNS server, as well as the parent resource of a group, may view and attach that server to a group.
Users with Admin permissions can access the DNS servers area under the DNS tab manage DNS server creation, edits, and deletion.
For more information on setting up permissions groups, see Users & Permissions.
Permission Shortcut Button ("Perms")
Throughout DNS, a shortcut permissions button ("Perms") is available on a per-item level, accessible only to Admin users.
This permissions button allows for direct, point-of-use permissions adjustments to DNS groups, servers, zones, and records. It uses the same CRUD permissions and groups available in the Admin Users tab, but removes the need to remember and search for the DNS item name.
To open the Change Resource Permissions module, click on the "Perms" Button for any DNS item.
Edit the CRUD permissions for any user group by clicking the checkbox for the desired group and permission type. When done, click "Save Changes". The permission changes will be also be reflected in the Admin User tab Group settings.
DNS Approvals
The Approvals module stores and queues DNS actions made by selected User Groups, and sends those actions to a Pending Changes list for administrative review. Later, an administrator (or combination of administrators) can approve or reject these stored actions.
Approvals is primarily set up and managed via the Admin Approvals Tab. See the ProVision Admin Guide - Approvals Tab for details on setting up and using Approvals from the Administrative viewpoint.
In the DNS Tab, a "Resources Awaiting Approval" module will display near the top of DNS Groups, DNS Zone Lists, and DNS Servers pages, if a change has been submitted on that page that is pending approval.
Users who submitted a change for approval will see the details of their change request in this module.
Admin users with permissions to approve or reject the request will have the option to Approve or Deny the change.
DNSv3 Workflow
DNSv3 revolves around groups. Zones are gathered under groups, servers attached to groups, and pushes may be done on a per group level. Thus, the first workflow step in DNSv3 is to set up one or more DNS groups. A "Default Group" is automatically provided in ProVision, but other groups may be desired to organize zones and default values.
To create a new DNS group, click the "Add Group" button from the DNS Groups tab. Enter the desired default values for the group, and save. If only using the Default Group, ensure the default parameter values are set as needed. For more information, see Working with DNS Groups.
After groups have been set up, DNS servers should be added or settings verified. Admin users may add DNS servers from the DNS Servers tab "Add Server" button. Input the server information and save. Existing servers may be reviewed and edited by clicking on the server name in the DNS Server List. Once a server is created in ProVision, it may be attached to any DNS group under the group's "Attached Servers" module. Attaching a server to a group will allow for zones in that group to be pushed to the attached server(s). See Working with DNS Servers.
Next, add zones to your groups. Zones may be manually added under each group by clicking the "Add Zone" button in the DNS Groups or DNS Zones tabs, or it may be imported via DNS Importers into a selected group. Add the zone and record information, and save. See Working with DNS Zones for additional information.
Zones may only exist once per group, but may be duplicated under multiple groups. Zones may also be moved from group to group as needed.
At this point, all major components of the ProVision DNS system have been added - from here management tasks take over. Zones may be updated and moved to or from groups; Groups may be edited with different default values or servers, and pushes maybe be performed for an individual zone, a full group, or for an entire server. Pushes may be manual or scheduled for a future time through the Scheduler.
