Setting Server-wide DNS Templates

This page explains how to set server-wide DNS templates that can be used by any new DNS Zone added to the system. To manage DNS templates, click the DNS templates button in the System Templates area. The server global DNS templates are available to all clients that have not set up their own DNS templates. In the Server Global DNS Templates management page, you can add new server-wide DNS templates, edit and delete existing templates.

Creating a New Sever Global DNS Template

To create a global DNS Template, follow the steps below:

1. Enter a name in the Template name text box.
2. From the drop-down list, select the template type:
   • Forward for forward DNS zones
   • Reverse for reverse IPV4 DNS zones
   • Reverse IPV6 for reverse IPV6 zones
   • E.164 for E.164 DNS zones
3. From the drop-down list, select the template's availability:
   • Owned template
   • Wide template, which can be used by all clients.
4. Click the OK button.

WARNING

Wherever you want the domain name to be automatically replaced by the name of the newly created domain, enter [domain] in the domain name field.

In order to have an IP address automatically replaced, use the [ip] tag.

A new page will open where you need to define the DNS records and Template IPs. This is where you can view the list of DNS records included in the template. The following details are available:

• Host: The host name or IP address of every DNS record;
• Record type: The type of the DNS record;
• Value: Depending on the record type, this field displays an IP address, an alias, a name server, a host name, or a text;
• M: If you click the Modify icon, you can edit the details of the corresponding DNS record.

To add a new DNS record to the server global DNS template, select the Record type in the New DNS Record area and then click Add. To remove a DNS record from the template, select the corresponding checkbox and click the Remove Selected link. You can delete several DNS records at the same time. DNS Manager will ask you to confirm this operation before permanently deleting the records.

Adding Records to a DNS Template

To add a record to a DNS template, click the Add DNS records button in the template's management page. In the Add new record page that opens, select the record type and configure it taking into account the explanations below. DNS Manager also accepts internationalized domain names (IDN) - Internet domain names that contain non-ASCII characters. The following types of DNS records are available:

Click here to view records for forward DNS zones.

Record Type	Details
IP Address (A)	Maps a hostname to a 32-bit IPv4 address. Type A rules have the following format: hostname. IN A XXX.XXX.XXX.XXX where: - XXX.XXX.XXX.XXX is the IP address for the hostname. - hostname. is the zone name or one of its subdomains. Examples: domain.com. IN A 1.2.3.4 subdomain.domain.com. IN A 1.2.3.4 domain.com. IN A [IP] Click here for more info on this type of record.
AAAA Record (AAAA)	Maps a hostname to a 128-bit IPv6 address. AAAA rules have the following format: hostname. IN AAAA:AAAA:AAAA:AAAA:AAAA:AAAA:AAAA:AAAA where: - AAAA:AAAA:... is the IPv6 address for the hostname. - hostname. is the zone name or a subdomain. Examples: domain.com. IN AAAA abcd🔢ffff:0:12:3:ab1:aa subdomain.domain.com. IN AAAA abcd🔢ffff:0:12:3:ab1:aa Click here for more info on this type of record.
Certification Authority Authorization (CAA)	Specifies one or more Certification Authorities (CAs) allowed to issue certificates for the domain. Format: hostname. IN CAA flags tag value where: - flags = 0–255 (critical flag) - tag = ASCII string identifying the property - value = value associated with the tag The CAA record contains a flags byte and a tag–value pair (“property”). Multiple CAA records can coexist. Available tags: - issue – authorizes a CA to issue certificates - issuewild – authorizes wildcard certificates - iodef – URL for reporting policy violations Examples: example.com. IN CAA 0 issue ";" example.com. IN CAA 0 issue "letsencrypt.org" example.com. IN CAA 0 issuewild "comodoca.com" example.com. IN CAA 0 iodef "mailto:example@example.com"
Alias (CNAME)	Alias (canonical name) pointing one hostname to another. Useful for multiple services on the same IP (ftp.example.com, www.example.com), or multiple HTTP servers on the same host. Format: hostname. IN CNAME servername. where: - hostname. is the zone name or a subdomain - servername. is an FQDN inside or outside the zone Examples: ftp.domain.com. IN CNAME inside.domain.com. ftp1.domain.com. IN CNAME outside.zone.com. k1._domainkey.domain.com. IN CNAME dkim.zone.com. RFC 1034: If a CNAME exists at a node, no other data must exist at that node. Click here for more info.
Nameserver (NS)	Maps a domain name to its authoritative name servers. Format: hostname. IN NS servername. where: - hostname. is the zone or subdomain - servername. is an authoritative nameserver Examples: domain.com. IN NS ns1.example.com. domain.com. IN NS ns2.example.com. Best practice: at least two NS records for each public domain. Click here for more info.
Mail exchanger (MX)	Maps a domain to its mail exchange servers. Format: hostname. IN MX preference servername. where: - hostname. = zone or subdomain - preference = priority (lower = higher priority) - servername. = mail server FQDN Examples: mail.domain.com. IN MX 10 domain.com. webmail.domain.com. IN MX 5 domain.com. Click here for more info.
Text record (TXT)	Allows arbitrary text in DNS. Used for SPF, DKIM, DMARC, verification, etc. Format: hostname. IN TXT "Text" Examples: domain.com. IN TXT "k=rsa; p=MEwwDQYerwqEWwE" subdomain.domain.com. IN TXT "this is a test" Click here for more info.
Service Record (SRV)	Specifies location of a service (protocol, port, target). Format: _Service._Protocol.Hostname. IN SRV TTL Priority Weight Port Target Parameters: - Service – symbolic service name - Protocol – TCP/UDP - Hostname. – domain - TTL – time to live - Priority – lower = higher priority - Weight – load balancing - Port – port number - Target – target hostname (not CNAME!) Examples: _service._tcp.domain.com. IN SRV 0 1 9 subdomain.domain.com. *._tcp.domain.com. IN SRV 0 0 0 . Click here for more info.
NAPTR Record (NAPTR)	Naming Authority Pointer. Used for rewrite rules (ENUM, SIP, etc.). Format: order preference services flag regexp replacement Parameters: - order – processing order - preference – secondary sort - services – resolution service - flag – next lookup modifier - regexp – primary rewrite rule - replacement – fallback rewrite rule Examples: domain.com. IN NAPTR 100 10 "u" "sip+E2U" "!^.$!sip:information@foo.se!i" . subdomain.domain.com. IN NAPTR 102 10 "u" "smtp+E2U" "!^.$!mailto:information@foo.se!i" . Click here for more info.

Click here to view records for reverse DNS zones.

Record Type	Details
Nameserver (NS)	Specifies a host which should be authoritative for the specified class. For class C reverse zones, NS records for $ORIGIN are accepted and classless delegation records are supported (RFC 2317, chapter 4). Important notes: • NS records for $ORIGIN appear bold in the interface. • A primary nameserver can be selected for zones (required by some local TLDs). • At least one NS must exist for $ORIGIN — recommended minimum is two for public domains. Class behavior: • Class A & B: NS records supported for $ORIGIN and inferior zones. Classless delegation not supported. • Class C: Classless delegation supported. DNS Manager can auto-generate matching CNAMEs if Automatically generate is enabled (available when subnet mask < 24 → numerical value > 24). Record format: ip_part.host_ip_addr.in-addr.arpa. IN NS servername. Where: • host_ip_addr.in-addr.arpa. → zone name • ip_part → remainder of the IP completing the address (varies by class) • servername. → authoritative nameserver hostname Examples: 1.2.3.in-addr.arpa. IN NS ns2.server.com. 1.2.3.in-addr.arpa. IN NS ns3.server.com. 0.1.2.3.in-addr.arpa. IN NS example.com. Click here for more information.
Reverse record (PTR)	Maps an IPv4 address to a hostname → used for reverse DNS lookup in the in-addr.arpa. domain. Record format: IPaddress IN PTR hostname. Where: • IPaddress → IPv4 address under IN-ADDR.ARPA • hostname. → forward hostname associated with that IP Example: 5.1.2.3.in-addr.arpa. IN PTR test.com. Click here for more information.
Alias for record (CNAME)	Canonical name alias mapping (supported only in Class C reverse zones, per RFC 2317). Record format: ip_part.network.host_ip_addr.in-addr.arpa. IN CNAME ip_part.host_ip_addr.in-addr.arpa. Where: • ip_part → IP completion segment • network → subnet mask • host_ip_addr.in-addr.arpa. → zone name Examples: 0.1.2.3.in-addr.arpa. IN CNAME 0.0.1.2.3.in-addr.arpa. 1.1.2.3.in-addr.arpa. IN CNAME 1.0.1.2.3.in-addr.arpa. 7.1.2.3.in-addr.arpa. IN CNAME 7.0.1.2.3.in-addr.arpa. Click here for more information.
Text record (TXT)	Stores arbitrary text — supports SPF, DomainKeys and other DNS-metadata functions. Record format: ip_part.host_ip_addr.in-addr.arpa. IN TXT "Text information" Where: • ip_part → completion segment of the IP • host_ip_addr.in-addr.arpa. → zone name • "Text information" → any text payload Example: 4.1.2.3.in-addr.arpa. IN TXT "This is a test" Click here for more information.

Click here to view record types for reverse IPV6 dns zones

Record Type	Details
Nameserver (NS)	Specifies an authoritative nameserver for an IPv6 reverse zone. NS records may be defined only for $ORIGIN. Record format: ipv6_part.host_ipv6_addr.IP6.ARPA. IN NS servername. Where: • ipv6_part → completes the IPv6 address when prepended to host_ipv6_addr • host_ipv6_addr.IP6.ARPA. → zone name • servername. → authoritative nameserver hostname Examples: 1.0.2.3.4.5.6.7.8.9.0.1.2.3.4.5.6.7.8.9.0.A.B.C.D.E.F.IP6.ARPA. IN NS example.com. 5.5.1.3.2.1.0.2.3.4.5.6.7.8.9.0.1.2.3.4.5.6.7.8.9.0.A.B.C.D.E.F.IP6.ARPA. IN NS example.com. For more details, see RFC 4291.
Reverse Record (PTR)	Maps an IPv6 address to a hostname → implements reverse DNS lookup in the IP6.ARPA domain. Record format: IPv6_address IN PTR hostname. Where: • IPv6_address → IPv6 reference in IP6.ARPA • hostname. → resolved canonical hostname Examples: 8.b.d.0.1.0.0.2.IP6.ARPA. IN PTR test.com. 1.1.1.1.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. IN PTR test.com. *.1.1.1.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. IN PTR test.com. For more details, see RFC 4291.

Click here to view record types for E.164 zones.

Record Type	Details
Nameserver (NS)	Maps a domain name to authoritative DNS servers. NS records are required for delegation. Record format: hostname. IN NS servername. Where: • hostname. → zone name or subdomain • servername. → authoritative nameserver Examples: 1.2.e164.arpa. IN NS ns1.example.com. 1.2.e164.arpa. IN NS ns2.example.com. 5.1.2.e164.arpa. IN NS ns1.example.com. Additional notes: • $ORIGIN NS records appear bold in interface • At least one NS required per zone (recommended minimum 2 for public domains) • Primary selection available in DNS Manager UI More info: IETF
NAPTR record (NAPTR)	Naming Authority Pointer record — used for URI resolution and rewriting, especially for telephony (ENUM). Record format: order preference services flag regexp replacement Where: • order → evaluation order when multiple records exist • preference → priority among identical order values • services → resolution protocol (e.g. sip, smtp) • flag → affects next DNS lookup stage • regexp → rewrite rule logic • replacement → fallback replacement string Examples: 1.2.e164.arpa. IN NAPTR 100 10 "u" "sip+E2U" "!^.*$! sip:information@foo.se!i" . 1.2.e164.arpa. IN NAPTR 102 10 "u" "smtp+E2U" "!^.*$! mailto:information@foo.se!i" . More info: IETF

Managing a Template's Ips

To access the Template's IP Management page, select the template in the list and then click the Template IPs button. This page displays the template's IPs and lets you add new IPs. The existing IPS are listed with the following details:

• T: Refers to the IP address type. It can be master or allow transfer.
• IP address: If the IPs list is too long, you may use the Search to find a specific IP more quickly.
• Search: Enter the criteria in the text box and click the Search button.

To add an IP to the template, follow the steps below:

1. Go to the Add Template IPs area and enter the IP in the appropriate field.
2. Select one of the following options:
   • Add the following master IP: for master IPs assigned to slave zones. You can add multiple IPs by pressing the button.
   • Add the following allow transfer IP to master zones: for allow transfer IPs assigned to master zones. You can add multiple IPs by pressing the button.
3. Press OK when you're done.

""

You can use both IPv4 and IPv6 addresses for transfer.

To set the template's availability, you have the following options:

• Owned templates (icon), which cannot be used by other clients.
• Wide templates (icon), which can also be used by other clients.

To switch from owned to wide templates, press their corresponding icon. dnsmanager500\