Netcup CloudDNS Support

[lukasp]

Hello Cloudron Team,

I am currently setting up Cloudron on a VPS at Netcup and ran into an issue with the Netcup DNS integration.

My Netcup account uses CloudDNS. The domain is configured with the current Netcup CloudDNS nameservers:

netcup.firstns.cc
netcup.secondns.at
netcup.thirdns.de
netcup.fourthns.systems
netcup.fifthns.com

Cloudron 10.0.3 does not initially recognize these nameservers as Netcup nameservers. The current implementation in src/dns/netcup.js appears to still check for the legacy Netcup nameservers / dns.netcup.net.

I temporarily modified this check to accept the current CloudDNS nameservers. After doing so, the next error was:

Netcup DNS error [5028] Can not update (all) DNS records for zone.
The zone hallecloud.de could not be found.

After looking into this, it appears that the current Cloudron integration uses the legacy Netcup DNS API.

Netcup now distinguishes between:

Legacy DNS: Legacy API Key + Legacy API Password
CloudDNS: API Key

My CloudDNS account therefore provides a CloudDNS API key, but does not have the legacy API credentials expected by the current Cloudron integration.

The Netcup documentation also appears to confirm this distinction.
My questions:

Is support for the current Netcup CloudDNS API planned for the Netcup DNS provider in Cloudron?

If not, is there currently a recommended way to use CloudDNS with Cloudron through the current API?

As a workaround, I switched to Cloudflare.

However, native CloudDNS support would obviously be much more convenient, especially because Cloudron could then automatically manage DNS records when installing applications or making DNS-related changes.

It seems that the existing Netcup integration would primarily need to be adapted to the new CloudDNS authentication method and the current CloudDNS nameservers.

Thank you for looking into this. I would appreciate any information on whether CloudDNS support is planned or whether there is another recommended approach.

Best regards
Lukas

[girish]

@lukasp we have ordered a new domain at netcup to figure out how to use this new CloudDNS and what the new nameservers are. We didn't get any response from support so far.

[girish]

Even the new domain is on the old DNS afaict .

[lukasp]

That is interesting...

[m-si]

I do have sort of the same problem. After years of working with netcup DNS, DNSSEC stopped working a few days ago. After haveing a conversation with their support, they told me that they no longer make DNSSEC available on their legacy DNS, so I was asked to migrate to their new DNS. After examining this I found that the new cloudDNS obviously is only supporting Key without an additional Password. For the user they documented the new cloudDNS here https://www.netcup.com/de/helpcenter/dokumentation/domain/dns-einstellungen-cloud-dns. It seems they are phaseing out their legacy DNS ...

So if cloudron plans to support netcup DNS automation any further, there needs to be a new implementation of their cloudDNS be done for cloudron (ideally during the phase out both of them available on the interface)…

the API documentation is this https://www.netcup.com/en/helpcenter/documentation/netcup-api (although I am not shure if this is the new cloudDNS or the old legacy DNS)

For me and other netcup users it would be awsome if cloudron keeps the support for netcupDNS as this made handling DNS very convenient. As I still enjoy the old prices of their servers... Which now – as hetztners – went up almost double the price they previously had… so +1 for lukasp

@girish maybe if you ask their support to upgrade the server you bought to the new cloudDNS for testing they will... (I think it is in netcups interrest aswell that you guys are able to use their new API and test it)

[girish]

@m-si said:

After haveing a conversation with their support

how did you manage this ? over email? or via https://www.netcup.com/en/helpcenter/support ? We emailed them two months ago and no response despite multiple tickets.

[girish]

Ha, I managed to reached them on the phone at +49 721 754 0 755 0. I haven't made a phone call in ages, so I was a bit shocked someone answered They said they will resolve the issue in 20 mins. Let's see.

[girish]

OK, I got a response - "Unfortunately, I am currently unable to convert your domains; an error occurs. I will forward your request to the appropriate department."

[timconsidine]

I’m bit confused.
I thought ClouDNS is separate independent service. That’s how I use them anyway.
I’ve not come across “Netcup ClouDNS”.
Do they have a tie up ?

[m-si]

@girish ahh so thais might take some time. but at least you reached a human … looking foreward. Would be awesome if you guys would have access to test instance.

@timconsidine check the links I posted in my previous post...maybe that lightens it up a little. I think netcup simply named their service somewhat alike clouDNS as they talk about CloudDNS (with double d)

[timconsidine]

Aha !
Now I see.