Creating a Resource Type for DNS Hosting

Before creating DNS hosting resource types, you must learn about the types of DNS services supported by CloudBlue Commerce. There are two types of DNS services:

• Ordinary DNS services

  • Name servers of these DNS services are registered in the system, and the system has the public hostnames and IP addresses of these name servers.

  • In DNS hosting resource types, you can specify name servers of these DNS services in activation parameters. DNS zones are created on those name servers that are specified.

• Name server suppliers

  • Only DNS services are registered in the system. Name servers of these DNS services are not registered in the system.

  • In DNS hosting resource types, you can specify these DNS services in activation parameters, without specifying their name servers. When creating a DNS zone, these DNS services allocate name servers from a name server pool. As a result, the system obtains the public hostnames and IP addresses of the name servers for that DNS zone after its creation.

In this CloudBlue Commerce version, the following DNS services are supported:

• Azure DNS (a name server supplier)

• BIND (an ordinary DNS service)

Note: During the installation of CloudBlue Commerce, a DNS hosting resource type is automatically created. You can adjust this resource type or create a new one.

To create a resource type for DNS hosting, perform the following steps:

1. Go to Products > Resources.
2. Click Add New Resource Type.
3. Select the DNS Hosting resource class.

4. Specify the following general parameters:

   • Name: This defines the name of the resource type.
   • Description: This defines the description of the resource type.
5. Click Next.

6. Specify the following activation parameters:

   • Auto host domains (Yes or No): This defines whether to create a DNS zone for a domain in the following situations:

     1. When a hosting service is added to a domain by using the pem.bindServicesToDomain Public API method.
     2. When a subscription upgrade or migration is performed by using the pem.upgradeSubscription or pem.migrateSubscription Public API method.
     3. A domain and a hosting service are added together by using the pem.addDomain Public API method.

     Note: If you modify the Auto host domains parameter value, the new value is applied to all new and old subscriptions containing this resource type.

   • Nameserver supplier: This defines a name server supplier. If you do not plan to use a name server supplier, select No nameserver supplier.

   • First nameserver, Second nameserver, and Third nameserver: These define the name servers where DNS zones must be created. If you do not plan to use a specific name server, select No nameserver.

     After specifying name servers, specify which type they will be (primary or secondary). Secondary name servers synchronize DNS zones with primary name servers. For example, you can use one of the following configurations:

     The first name server	The second name server	The third name server
     Primary	Primary	Primary
     Primary	Secondary	Secondary

     Notes:
     
     1. The name server in First nameserver is always primary.
     
     2. Name servers appear in DNS zone files in the order specified.

   • Refresh: This defines the interval in seconds at which secondary name servers will query primary name servers to detect and obtain DNS zone updates.

   • Retry: This defines the number of seconds after which secondary name servers will retry to request DNS zone updates from primary name servers if these primary name servers do not respond.

   • Expire: This defines the number of seconds after which secondary name servers will stop processing DNS queries for a DNS zone if its primary name servers do not respond.

   • Default TTL: This defines the default value for the TTL parameter of DNS records (in seconds).

   • Mailbox of the person responsible for DNS zones: This defines the email address of the administrator responsible for a DNS zone. If not specified, CloudBlue Commerce uses the email address of the account under which a domain is provided with a DNS zone. If specified, all DNS zones based on this resource type obtain the specified email address.

7. Click Next.

8. Check the specified parameters and click Finish.