Can't use Heliohost Nameservers on Namecheap

[rsd]

Hi,

firstly thanks for providing all of this for free.

However I'm having trouble using my domain to access my website.

 

What I did:

Under Namecheap Dashboard / Domain / Nameservers / Custom DNS entered "ns1.heliohost.org, ns2.heliohost.org".

 

What happens:

After a while ( I'm assuming when it eventually tries the new setup and fails ) it automatically switches back to BackupDNS of Namecheap, and the cPanel tools complain about it when I try to add the domain.

 

Why it happens:

I have contacted Namecheap Support about the issue and I was told that "ns1.heliohost.org and ns2.heliohost.org have not been registered yet, thus, ****.de cannot be pointed to the nameservers." and that I should contact my DNS provider and ask them to "register ns1.heliohost.org , ns2.heliohost.org according to the requirements of the Registry.Thus, a minimum of 2 authoritative independent DNS is required. It means that the IP-addresses of each nameserver should differ by at least one number in any octet. Also at least one of them must be connected via IPv4."

 

Relevant Information :

domain name : ****.de
username : rsd
server name : johnny

 

Thanks in advance.

[Bailey]

Can you send us a screenshot of where you have entered the namesavers please.

[Bailey]

And ns1.heliohost.org and ns2.heliohost.org have been registered because everyone else uses them.

[rsd]

Thanks for the fast response. I'm just forwarding what they said, all I know is it somehow doesn't work in my case.

 

Screenshot:

https://i.imgur.com/Abfx4vg.png

[miwilc]

Hmm.

Your current NS points to both namecheap and heliohost, this is not supported remove/disable the namecheap DNS (ref: image)

https://s10.postimg.org/675nil02x/Screenshot_20171226-105607.png

The heliohost NS is:

 

ns1.heliohost.org

ns2.heliohost.org

 

I recommend ordering namecheap staff to manually set the nameservers to ours or transfer out to a registrar like https://www.namesilo.com

 

 

@Krydos it appears that namecheap is disallowing the same IP for both nameservers, which is weird that they would completely disallow using NS servers for that. They should've just issued a warning.

[rsd]

I have contacted Namecheap support again, and they insisted that the .de domains can't be directed to DNS that don't follow the Registry rules and that manually setting them would still revert back to the BackupDNS automatically. They also told me that I can check the status on https://www.denic.de/en/service/tools/nast/ (which is the manager of the .de domain)

About changing the provider, as far as I know Namesilo doesn't offer .de domains and even if it did I am reluctant to change as I have been very happy with Namecheap so far.

Would it be possible to fix the issue on your side (I assume by assigning a different IP to the second nameserver) ? What can I do meanwhile until the issue is fixed ? I have unsuccessfully attempted a CNAME record, which only works from subdomains, but it directs to the Account Queued page instead.

[wolstech]

If I remember right, .de is like .br...it can't be hosted here without jumping through hoops. It's to do with the fact that our system requires the NS be set first, and those two TLDs require the host be set up first. These two TLDs are backwards vs. everyone else out there.

 

The fix is to change your main domain to the .de domain, set the name servers at namecheap, change the main domain back, then add the domain as an alias or add on domain. I'd suggest trying this for your .de and see if it works. You can change your account's main domain here: http://www.heliohost.org/classic/support/scripts/domain

[Bailey]

The iP addresses are different. I think it's a problem on your behalf. Everyone else seems to be working fine

 

Edit: @wolstech went into more detail. We posted at the same time.

[rsd]

Thank you wolstech, that makes a lot of sense. I'll try doing that and report here in case it doesn't work (or just edit the message if it does).

Sorry Bailey, I assumed otherwise based on namecheap and miwilc's message, my mistake.

 

EDIT : It does work and without any issues so far! Thanks again for all the help. (28.12)

Edited December 28, 2017 by rsd

[Bailey]

No worries, I wasn’t totally correct though, turns out the problem is with the way .de[/] TLDs do things. Meaning that it’s not our fault or yours.

[Krydos]

@Krydos it appears that namecheap is disallowing the same IP for both nameservers, which is weird that they would completely disallow using NS servers for that. They should've just issued a warning.

ns1 = 65.19.143.3

ns2 = 64.62.211.133

 

They are definitely quite different IP addresses. I have registered several paid domains, including krydos.com, through namecheap and haven't had any issues using HelioHost nameservers.

 

Wolstech probably has it right. Our servers require the nameservers to be set before you can add the domain, and the domain requires the nameservers already host the domain before the nameservers can be set. Luckily changing your main domain doesn't use the same nameserver checks as addon or alias domains through cpanel.