Page tree

This page explains how to add a single or multiple DNS Zones. 

Overview

To add a new DNS Zone, click the Add DNS zone button under Tools. In the page that opens, click the name of the client who will be the owner of the new DNS zone.

You can add a single DNS Zone to the Client account, multiple DNS zone names from a local file or multiple DNS zones with complete DNS records.

DNS Manager also accepts internationalized domain names (IDN) - Internet domain names that contain non-ASCII characters.

Adding a single DNS zone name

In order to add a single DNS Zone name, you need to enter all the information required in the Add DNS Zone name section of the page.

DNS Zone name: Enter a valid DNS zone name that is unique in the system. You can add a Forward zone, a Reverse zone or an E.164 Zone. The name must be unique in the system. 

DNS Manager implements an algorithm to avoid zone hijacking. When a zone is added (subdomain.test.tst), DNS Manager checks if that zone is a substring/part of an already defined zone (test.tst).

If the already defined zone (test.tst) belongs to the same client as the new zone (subdomain.test.tst), then the zone is added.

If the already defined zone (test.tst) belongs to another client than the one who wants to add the new zone (subdomain.test.tst), DNS Manager checks if there is a delegation for the new zone (subdomain.test.tst) in the old zone (test.tst), namely a NS record that delegates subdomain.test.tst. If the record exists, then the new zone (subdomain.test.tst) can be added. If the special delegation is not defined, then the new zone won't be added with the message "Zone cannot be added because it is already managed by another client on this server."

For Forward Zones, use the <lower level domain(s)>.<top level domain> format.

Examples:

  • racksoft.com
  • wikipedia.org
  • amazon.co.uk

For Reverse Zones, use the <lower level domain(s)>.IN-ADDR.ARPA format or <lower level domain(s)>.IP6.ARPA.

Examples:

  • 2.85.64.IN-ADDR.ARPA
  • 4.3.2.1.IN-ADDR.ARPA
  • 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.IP6.ARPA

For E.164 Zone, use the <lower level domain(s)>.E164.ARPA format.

  • 2.2.3.E164.ARPA
  • 1.1.1.E164.ARPA

For Reverse zones, DNS Manager accepts the following zone name types:

  • Class A (/8) - 1.IN-ADDR.ARPA
  • Class B (/16) - 2.1.IN-ADDR.ARPA
  • Class C(/24) - 3.2.1.IN-ADDR.ARPA
  • Zone names with a mask lower than 24 (having a numeric value higher than 24) - 192/26.1.2.3.IN-ADDR.ARPA that covers IPs between 3.2.1.192 and 3.2.1.255; or 4.3.2.1.IN-ADDR.ARPA for a complete /32 delegation.
  • IPv6 addresses - 8.b.d.0.1.0.0.2.IP6.ARPA

Prior to RFC 2181 '/' was not a legal character for a domain name or label so an alternate construct using '-' could be used instead, that's why DNS Manager supports both characters.

  • DNS Zone template: You can use the DNS Zone templates available or you can choose not to use any template at all.

  • Template IP: This field is available when a DNS Zone template is selected. All occurrences of [ip] in the DNS Zone template will be replaced by this IP.

  • DNS Zone type: The type of the DNS Zone can be master or slave.

A slave zone will acquire it's zone data only after receiving the notification from the respective master zone, or after it is manually reloaded on the server. 4PSA DNS Manager does not reload slave zones due to the extra overhead involved on busy environments, therefore is recommended to setup notifications on master zones.

When the chosen type is master, the Allow DNS Zone transfer option becomes available and the Slave DNS servers IP addresses option is disabled. When the chosen type is slave, the Transfer DNS Zone from master servers option is enforced and the Master DNS servers IP addresses option becomes available.

  • Forward Zone: When this option is enabled, this is considered to be a regular zone.
  • Reverse Zone: When this option is enabled, this is considered to be a zone used for reverse DNS lookup (i.e. a zone in the in-addr.arpa domain or ip6.arpa).
  • E.164 Zone: When this option is enabled, this is considered to be an E.164 zone used for mapping telephone numbers into DNS (i.e. a zone in the e164.arpa domain).
  • Allow DNS zone transfer: When this option is enabled, allowed slave servers will be able to retrieve the Zone information from the master server (in this case the 4PSA DNS Manager system). 
  • Slave DNS servers IP addresses: When the Allow DNS Zone transfer option is enabled, you can enter the IP addresses of the slave DNS servers in this text box. Click the plus/minus icons to add/remove slave IP addresses. The DNS Zone will be transferred only to these IP addresses.

When the chosen type of the DNS Zone is slave, you need to enable the following options:

  • Transfer DNS zone from master servers: The DNS Zone information will be transferred from the master DNS servers with the IP addresses set in the field below.
  • Master DNS servers IP addresses: Use this text box to specify the IP addresses of the master DNS servers.

    You can use both IPv4 and IPv6 addresses for transfer.

The required fields are marked with an asterisk. Click OK to create the new DNS Zone. Click Cancel, if you want to return to the previous page without creating the DNS Zone.

Adding multiple DNS Zones with complete DNS records

In order to add multiple DNS Zones with complete DNS Records, click the Add DNS zones button.

In the DNS Zone management page, click the name of the client who will be the owner of the new DNS Zone, then click the Full zones from file button available in the Tools area. The following fields will be displayed:

  • Select file: Enter the name of the file that contains the DNS Zone names or click the Browse button to locate the desired file.

The uploaded file MUST be in dump format (identical to the file generated by backing up DNS zones in 4PSA DNS Manager). For more information on the dump file format, please read the Supported Dump File examples appendix.

A slave zone will acquire it's zone data only after receiving the notification from the respective master zone, or after it is manually reloaded on the server. 4PSA DNS Manager does not reload slave zones due to the extra overhead involved on busy environments, therefore is recommended to setup notifications on master zones.

  • Allow DNS zone transfer: When this option is enabled, allowed slave servers will be able to retrieve the Zone information from the master server (in this case the DNS Manager system).
  • Add the following allow transfer IP or IP/Mask to master zones: The IP addresses specified in this field will be recorded in the allow transfer clauses of the named.conf file for MASTER DNS zones.
  • Add the following master IP: The IP addresses specified in this field will be recorded in the masters clauses of the named.conf file for SLAVE DNS zones.

    You can use both IPv4 and IPv6 addresses for transfer.

Click OK to create the new DNS Zone. Click Cancel, if you want to return to the previous page without creating the DNS zone. This may take some time depending on the size of the file you have specified.

#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 4.0 International.