Search Engine: Elastic

Article ID: 112794, created on Nov 11, 2011, last review on Apr 24, 2015

  • Applies to:
  • Operations Automation 5.3


A domain is registered through PBA-E together with a subscription for other services. Two separate subscriptions are created based on two separate service templates, both of which include a DNS hosting resource. This resource is assigned during the domain registration. However, respective name servers do not host corresponding DNS zones.There is no domain zone file on the name servers.

The POA background task "Update named" fails with the following error:Last execution output   Multiple errors during NS update: Internal error: /usr/sbin/rndc /usr/sbin/rndc reload failed with code 1 saying: STDOUT: '' STDERR 'rndc: 'reload' failed: not found'.


1. During domain registration, PBA-E sends a request to POA to put the corresponding zone on the name servers temporarily. This is required for the domain registration process, during which the registrar may verify domain availability on the authoritative name servers.
2. In a separate thread, another service is provided as long as the second service template does contain a DNS hosting resource. An "Auto host domains" configuration parameter is turned on, and POA creates a DNS zone for the domain automatically.
3. Since these actions are performed asynchronously, a race condition may occur when the DNS zone created during the sequence described in #2 interferes with the sequence described in #1.


Edit a service template for other services and set the parameter "Auto host domains" to "No" as shown in the following screenshot:

2554725ed606193dd9bbce21365bed4e 5356b422f65bdad1c3e9edca5d74a1ae a8cdca46e4357a6e38fded820770e272 caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF