...
(CFR denotes customer requested)
DNSv3
IM - XXXX2552: Updated backend efficiency and created a and replaced the DNS Admin and DNS Tabs with DNSv3 - featuring a more efficient backend, new user interface for the DNS Tab. , and a DNS "Group" system.
- Access DNS Servers, Groups, and Zones from the same ProVision DNS tab.
- Removed the DNS-Admin tab. Functionality previously in DNS-Admin is now contained under the DNS tab "DNS Servers" area (Admin only), with SOA and Nameserver defaults set per-Group.
- Introducing "DNS Groups" - Organize your Zones and Servers together into a single place. With Groups, you are able to push whole group configurations at the same time.
- Zone Error Monitoring - Check zones for errors, and receive detailed feedback.
- Schedule Pushes at the server, group, or individual zone level.
Peering "View By Peer" tab
| Expand |
|---|
To see "View by Peer", navigate to the ProVision Peering Tab. At the top left of the page, click the "View by Peer" button.
On the "View by Peer" page, click on a Peer from the list on the left. You may also filter the list by typing a few characters from the Peer name into the filter box. Once a Peer is selected, View information and sessions for that peer by clicking on the "Info" and "Sessions" tabs at the top of the center information panel.
When done, return to the main Peering Tab by clicking on the "View by Exchange" toggle at the top of the page. |
Additional Features / Improvements
InfoBlox DNS Zone Import
New DNS Import Options
Provision ProVision DNSv3 supports the addition of Infoblox as a DNS server type, and adds an InfoBlox DNS four new DNS Zone Import option options to the Admin Admin Data Import Tab. Tab:
InfoBlox DNS Zone Import
| Expand |
|---|
To import zones from an Infoblox server, navigate to the Admin area Data Import Tab, and click on "InfoBlox Zone Import". From there, fill out information for the Infoblox server host, username, and password. Select the Import options for zone type, view, and DNS Group.
When done, click the "Import" button. |
DNS APIv1 Updates
To support the release of DNSv3, the following updates have been made to DNS APIv1 endpoints:
...
NS One DNS Zone Import
Expand To import zones from a NS One server, navigate to the Admin area Data Import Tab, and click on "NS One Zone Import".
From there, enter the NS One API Key and select the desired DNS Group to add the zones under.
When done, click the "Import" button.
DynDNS Zone Import
Expand To import zones from a Dyn DNS server, navigate to the Admin area Data Import Tab, and click on "Dyn DNS Zone Import".
From there, enter the DynDNS Customer Name, UserName, and Password, then select the desired DNS Group to add the zones under.
When done, click the "Import" button.
DNSMadeEasy Zone Import
Expand To import zones from a DNSMadeEasy server, navigate to the Admin area Data Import Tab, and click on "DNSMadeEasy Zone Import".
From there, enter the DNSMadeEasy API Key and API Secret, then select the desired DNS Group to add the zones under.
When done, click the "Import" button.
...
CPNR Updates:
CPNR Updates include:
- Added a check to ensure CPNR modules in ProVision are reachable prior to Push
- Option 43 is now integrated
- scope_upsert call now is taking 2 new parameters "option_43_name" and "option_43_value".
- The "option_43_name" must be predefined inside CPNR (Design->Options)
- "option_43_value" should be the value that is going to be set for the Scope for example "241 11.22.33.44" (typically 241 followed by the IP).
DNS APIv1 Updates
To support the release of DNSv3, the following updates have been made to DNS APIv1 endpoints:
- As of DNSv3, zones are now considered their own resource. Thus, DNS APIv1 zone parameters "zoneResourceId", "updateZoneResourceId", and "deleteZoneResourceId" now refer to (and equal) the zone ID instead of the parent resource ID, and are no longer editable values.
- The DNS Zone Control "GET" optional parameters "selectOffset" and "sortArray" have been removed.
- DNS Zone Tags are no longer supported. Zone Tag parameters under target=zone and target=record have been removed.
IPAM APIv1 Updates:
Get:The following updates have been made to IPAM APIv1 "get" endpoint. Valid tagsMode options are now "strict", "exclude", "intersection", and "union". See API Module - IPAM for additional details.
...