Search Engine: Elastic

Article ID: 124226, created on Jan 20, 2015, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation


I am planning to create new service templates for hosting various services, including DNS. Are there any best practices on how to combine different services into service templates? I want to have a flexible and yet stable configuration.


Yes, there are certain things to consider when creating service templates that include or require "DNS Management" resource type, which are not described in POA Provider's Guide.

For example, "DNS management" resource can become "broken" while adding/removing additional services/subscriptions that leverage one internet Domain (TLD).

To avoid that, If you want to provide DNS (Management), Web hosting and Mail hosting for customers, it is recommended that you create three separate service templates (ST):

  • ST1: With "DNS" and "DNS Management" resources
  • ST2: With resources needed for Web hosting (no DNS resources)
  • ST3: With resources needed for Mail hosting (no DNS resources)

In the above scenario DNS resources, when needed, will be taken from the first service template. Such approach will help you to avoid some drawbacks of the traditional service templates organization scheme, when all resources needed for the complete hosting package are placed into a single service template.

This MS Visio presentation provides more insight into the subject. It also shows concepts of Accounts, Domains and Subscription (services) and some thought about how API can aid you in growing and managing services that all need DNS management to provide those services.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF