Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Offical apps | Community apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Netcup CloudDNS Support

Netcup CloudDNS Support

Scheduled Pinned Locked Moved Unsolved Support
netcupdomains
1 Posts 1 Posters 37 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L
    L
    lukasp
    wrote last edited by joseph
    #1

    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

    1 Reply Last reply
    3

    Hello! It looks like you're interested in this conversation, but you don't have an account yet.

    Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

    With your input, this post could be even better 💗

    Register Login
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • Bookmarks
    • Search