[Solved] Can't Create New Addon Domain

[onipip]

username: onipip

domain: onipip.heliohost.org

server: johnny

 

I'm trying to create a new addon domain alterea.it

The domain is already up with nameservers ns1.heliohost.org and ns2.heliohost.org

I go in "Addon Domains", I insert all data needed, I click "Add Domain", and after 5 minutes the page goes timeout.

I check my account and I found:

 

- No addon domain has been created

- No ftp account

- There is a subdomain alterea.onipip.heliohost.org

- The folder alterea.it is up

- Advanced DNS zone editor says "Please refresh the page and try again"

- No traces of domain alterea.it on Simple DNS zone editor

 

I removed the subdomain (again 5 minutes, this time no timeout) and the alterea.it folder, Advanced DNS editor still offline.

After about 1 hour I tried again to create the addon domain, same scenario.

 

Can you fix the issues?

Greetings

[onipip]

Hi all.

At today the problem still persists, can someone help me?

 

Greetings

[Byron]

This support request is being escalated to our root admin.

[onipip]

After some months I relive this thread because I have some new info.

Apparently, the new Addon Domain cannot be created because the Name Servers are not correctly pointed to the HelioHost Name Servers: this condition stops midway the Addon Domain creation process, but the cPanel does not reports any error about this.

I contacted my domain registrar to ask why the NS are not changed to HelioHost, and it says that because the addon domain that I try to create is a ".it", the Italian Registrar Authority does more checks on Name Servers before authorizing the DNS change, i.e.:

 

- There must be st least 2 NS

- Both NS must be fully working

- Cannot be any error on any NS during the check

 

In detail, it seems that the Name Server ns2.heliohost.org does not responds correctly during the check:

 

<test name="NameserversResolvableTest" status="SUCCEEDED">
<nameserver name="ns1.heliohost.org." status="SUCCEEDED"/>
<nameserver name="ns2.heliohost.org." status="SUCCEEDED"/>
</test>
<test name="NameserversAnswerTest" status="FAILED">
<nameserver name="ns1.heliohost.org." status="SUCCEEDED"/>
<nameserver name="ns2.heliohost.org." status="FAILED">
	<detail queryId="4">Nameserver test skipped for error in query: java.net.SocketTimeoutException</detail>
</nameserver>
</test>

 

See also the full report.xml attached.

The problem does not seem temporary, because it persists from September.

Can the root admin check for problems on this NS (and anso the cPanel lost error)?

report.xml

[wolstech]

NS2 hasn't worked correctly since March. The root admin (the company's owner actually, not Krydos) was messing with both NS's last night...NS1 should be more reliable and NS2 is no longer crashed but is down much of the time anyway because it shares a server with Johnny.

 

One way to get this to work is to keep trying since it was fixed yesterday. At some point you'll find a time when both are up. Alternately, ask the registrar 's support if they can make the change without those checks. Registrars that have tests like these often don't set up correctly here, and you have to ask their support to change it for you instead (tell them you're aware of the broken NS2).

 

If their support won't/can't change it, you can always use A records and change your main domain instead.

[Krydos]

Yeah, I've been struggling with a mental block of how to fix the uptime with the Heliohost nameservers for a long time. Many thanks to Ashoat took a look with fresh eyes and fresh error logs that were being emailed to him that I didn't have access to. In simple terms it was the monitoring process that is responsible for keeping the nameservers online that ironically was causing the nameservers to be offline so often. It's like saying you need to go down if you want to go up, or turn left to go right. It just didn't occur to me because it was such an illogical solution.

 

Anyways, ns1.heliohost.org should once again have nearly 100% uptime, and ns2.heliohost.org should have better than 0% uptime as it has for the last several months. This should solve your issues of setting your nameservers on your registrar. Let us know if you need any further help.