Search Engine: Elastic

Article ID: 120992, created on Apr 10, 2014, last review on Dec 22, 2016

  • Applies to:
  • Odin Business Automation Standard 4.5

Symptoms

I'm trying to register a domain with registration plug-in InterNetX. A domain remains in status "Registering" (Top > Service Director > Domain Manager > Domains). The following records appear in DEBUG log (/var/log/hspc/hspc.log):

[2014/04/08 06:46:00] [DEBUG] [32444] [HSPC::Logger::sw_trace] TRACE [02]: . +> HSPC::MT::DM::ToolsInt->is_zone_started ()
[2014/04/08 06:48:30] [DEBUG] [32444] [HSPC::MT::DM::ToolsInt::is_zone_started] The zone(%domain.tld%) is not sarted yet on NS(123.123.123.1)
[2014/04/08 06:48:30] [DEBUG] [32444] [HSPC::MT::DM::ToolsInt::is_zone_started] The zone(%domain.tld%) is not sarted yet on NS(123.123.123.2)
[2014/04/08 06:48:30] [INFO] [32444] [HSPC::MT::DM::ToolsInt::is_zone_started] The zone already started?: no
...
[2014/04/08 06:48:30] [WARN] [32444] [HSPC::MT::DM::ToolsInt::process_regdomain_after_zonestart] [DM] WARNING: DNS zone starting timed out. Some NS servers for domain %domain.tld% may be unreachable. The next attempt #3 of 10 will be launched in 0 minutes.

Where 123.123.123.1 and 123.123.123.2 are name servers registered in Odin Business Automation - Standard (OBAS):

Top > Service Director > Domain Manager > Name Servers

Cause

It's by design that domain registration with InterNetX requires to start domain DNS zone at OBAS name servers before sending registration request to the registrar. Domain DNS zone is created in OBAS and synchronized with the name servers via periodic task "DNS Synchronization" (Top > Configuration Director > Logging and Errors > Action Log > Tasks Queue).

The issue might happen because:

  1. Both name servers 123.123.123.1 and 123.123.123.2 are Non-manageable name servers. They do not support automated zone files synchronization.

  2. It takes a long time to run “DNS synchronization”. Domain registration process that checks for zone started cannot wait for the end of the periodic task and the error appeared before synchronization is completed.

Resolution

  1. Register at least one SSH-manageable name server in OBAS.

  2. Increase limit "DNS zone startup time limit" in plug-in settings. For example:

    Top > Service Director > Domain Manager > Plug-ins > InterNetX > TLDs > %tld%: DNS zone start-up settings

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 624ca542e40215e6f1d39170d8e7ec75 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF