Editing zone contents is done in the zone details page, which is openend by clicking on the name of a zone in the main window.
Zone details page¶
This page lists all the DNS records in the zone in a table. Each row has the following elements:
Name**(**7) shows the exact name of this record. It is fully qualified, which means that it includes the parent zone’s name.
The Type field shows the type of the record.
TTL: The Time to Live value of this record, shown in a shorthand if possible. Possible value suffixes for this shorthand are: ‘H’ for ‘Hours’, ‘M’ for ‘Minutes’, ‘D’ for ‘Days’ and ‘W’ for ‘Weeks’. If no unit is present, the value is given in seconds.
The Records column shows the record’s data for Name and Type and contains several buttons to manipulate this record. 8 is a shortcut for 1 and opens the New record dialog window with the current domain prefilled. Pressing 9 slates the record for deletion and 10 opens the Edit record dialog. When the logged-in user’s permissions are insufficient, or when the zone cannot be edited (e.g. because it is a slave zone), these buttons are not visible.
When more than 200 records exists, the list is paginated. The page-controls are at the bottom of the records and the hotkeys ctrl+f and ctrl+b can be used to go a page forward or backbrad, respectively.
At the top of this window, next to the zone name, several buttons provide additional information about the zone. These buttons can be clicked to open a dialog window with relevant configuration items.
2 shows the DNSSEC state of the zone. It is green when DNSSEC is enabled and white when it is disabled. Clicking this button opens the DNSSEC dialog window.
The zone kind button (3) shows what kind of the zone this is. This is one of master, slave or native. Clicking this button opens the Zone kind dialog window.
Clicking the Export button (4) generates an export of the zone in zone file format. Your browser will offer to download this file.
The History button opens the zone history window, where all the past changes to this zone are listed, with the latest changes on top. This view can also be used to restore a previous version of the zone if necessary.
Any changes made to the zone in this window are not directy sent to the PowerDNS Authoritative Server, but kept within the browser. When there are pending changes, a button appears at the top of the window displaying the number of pending changes. Clicking this button opens the “Confirm Save” dialog.
If you close the browser window without saving, your pending changes will be lost.
Adding a new record¶
When adding a new record, several pieces of information need to be filled in.
Field 1 contains the name of the record. The name on the record must always be relative to the zone, as alluded to in the dialog. Leaving this field empty creates a record at the top of the zone.
The selector at 2 specifies the type of record that will be added. The buttons to the right of this field are shortcuts to frequently used DNS types.
The TTL field (3) sets the Time to Live for this record. This field accepts a number of seconds, or a shorthand notation like “10M” for a 10 minute (600 second) TTL. To the right you will find several shortcuts for frequently used TTLs.
In DNS, the TTL applies to the record set, not to a single record.
The Records field at 4 is used to input the contents of the record(s), one item per line.
You can prefix individual records with
; to disable them, in which case they will not be server by the DNS server.
Disabled records will be validated on save, just like active records. You cannot use this for adding arbitrary comments.
When adding IPv4 and IPv6 addresses (A and AAAA records), the IP addresses can be suffixed with a
* to indicate a PTR (“reverse”) record should be created for this address.
On save, the server will check if a zone exists to store the PTR. If none exists, the whole save transaction is aborted.
Check the box at 5 to schedule this change for the future. See the chapter on scheduled changes for more information.
Upon clicking the “OK” button, the new record is added to the pending changes.
Editing a record¶
After clicking the edit button (10 in Fig. 5), the Edit record dialog is opened.
This dialog is a stripped-down version of the New record dialog. The name and type of the record are fixed and shown in the header of the dialog.
The TTL field (1) sets the Time to Live for this record. The field accepts a number of seconds, or a shorthand notation like “10M” for a 10 minute (600 second) TTL. To the right you will find several shortcuts for frequently used TTLs.
In DNS, the TTL is per record set, not per single record.
The Records field at 2 is used to edit the contents of the record(s), one item per line.
Check the box at 3 to schedule this change for the future. See the chapter on scheduled changes for more information.
Saving pending changes¶
When editing, adding or deleting records, changes are not immediately saved to the DNS Server. Instead, these are ‘staged’ inside ZoneControl.
Changing DNSSEC settings¶
Pressing the DNSSEC button (2 in Fig. 5 or Fig. 6 when DNSSEC is disabled) opens the DNSSEC dialog.
By default NSEC will be used for DNSSEC. Checking the “use NSEC3” box will show an expanded dialog where one can edit the NSEC3PARAM.
Clicking the “Enable DNSSEC” button will enable DNSSEC for the zone. This adds cryptographic keys based on the settings of the PowerDNS Authoritative Server.
On a DNSSEC secured zone, the dialog displays the DNSSEC information that can be uploaded to the zone’s registry (see Fig. 13 for an example).
Both the DS records and DNSKEY record are shown. Which of these need to be uploaded depends on the domains’s registry. Some registries require the DNSKEY to generate the DS records themselves.
This dialog can also be used to update the DNSSEC settings or to disable DNSSEC. As part of updating the DNSSEC settings it is possible to switch between NSEC and NSEC3 (the cryptokeys will be kept). Clicking the NSEC3 radio button will show the expanded NSEC3 settings similar to those in Fig. 12.
It is possible to disable DNSSEC here but be very careful with this (as shown in Fig. 14) as we do not have backup functionality in place in this version of ZoneControl. The “Disable DNSSEC” button will be disabled until one enables it by pressing the red lock / unlock button.
The “Disable DNSSEC” button can be disabled again by pressing the, now green, lock button.
Clicking the Zone Kind button (3 in Fig. 5 or Fig. 7) opens the Zone Settings dialog window. The options available in this dialog depend on the zone kind.
Native zones have the fewest settings, as there are no settings required for data replication.
The button at 1 converts the zone from a native zone to a master zone.
Changing from a native zone to a master zone might require extra configuration in the PowerDNS Authoritative Server. For instance, the master configuration setting will need to be enabled before notifications are sent.
As it is possible for native zones to be replicated via AXFR, the field at 2 allows configuration of IP addresses that may transfer this zone.
For master zones, the dialog in Fig. 16 is displayed:
The button at 1 converts the zone into a native zone.
Converting into a native zone will make the PowerDNS Authoritative Server stop sending notifications for zone updates. It will still allow zone-transfers.
In field 2, IP addresses that are allowed to transfer the zone can be specified.
The IP adresses entered in the field at 3 will be notified when the zone has been changed, in addition to all the servers specified in the zone’s NS records.
The slave zone dialog is show in Fig. 17.
The field at 1 is used specify the IP addresses of the master(s) of this zone. These addresses can be suffixed with a port, should be it different from the default of ‘53’.
When adding a port to an IPv6 address, the address part must be wrapped in square brackets to disambiguate the address from the port:
If this server is also a master for other slaves, the other two fields can contain relevant settings.
In the field at 2, IP addresses that are allowed to transfer the zone can be added.
The IP adresses entered in the field at 3 will additionally be notified when the zone has been changed. By default all servers in the zone’s NS records are notified of changes.