Search Engine: Elastic

Article ID: 863, created on Oct 6, 2008, last review on May 26, 2014

  • Applies to:
  • Odin Automation
  • Odin Business Automation Standard 4.5

Automatic import from KB #863


First of all you have to create nameservers from PCC:


a) "full" hiding - ie. belongs to a reseller and an IP address of is also assigned to a reseller. It  happens rarely but it is possible. This usually means that it's somewhere outside, cannot be 'combined' with your nameservers and you have to use the option 'SSH-Managed nameserver':

*a reseller creates a nameserver somewhere and gives you login credentials. * you create a ssh-managed nameserver in PCC. * nameserver will have _all_ zones registered in HSPc, not only reseller's ones - HSPcomplete can't do 'partial sync'.

b) 'almost full' hiding - IP is one of yours but reverse resolving for that IP gives You have to add this IP address to your existing _manageable_ nameserver then to create a _non-manageable_ nameserver. -> IP and IP -> resolving should be configured. What you finally will have is a DNS server with 2 IP addresses which listens on both.

*) you add an IP address to a physical server / VE which is registered as a manageable nameserver in PCC. *) you create a non-manageable nameserver - again because HSPcomplete can't do 'partial sync' and you don't need to sync DNS twice.

c) 'no hiding' - you don't give a dedicated IP for a reseller's nameserver; only the>IP_of_your_nsserver is configured but not vise versa. In this case again you need to create a non-manageable nameserver.

Please decide which way is preferred and create at least 2 nameservers. Allow their usage for resellers. After that a reseller should create (from RCC) a set from these nameservers. The procedure will also "lock" this set and its members to a reseller's account.

When it's done, a reseller should mark this newly created set as a default and specify it in domain's manager general setup, in all hosting plans and in DNS templates.

400e18f6ede9f8be5575a475d2d6b0a6 8fc71f07abe5b233fea1ae0377cd5e3d 624ca542e40215e6f1d39170d8e7ec75 70a5401e8b9354cd1d64d0346f2c4a3e 3ef1f5f998c0dc182718a7fe4376f875

Email subscription for changes to this article
Save as PDF