Skip to content
betaDNS betaDNS hostingSetup guide checked 2026-09-27

netcup

netcup API key setup: create Legacy DNS credentials in the CCP; the current DNSMigrator adapter does not accept a CloudDNS API key.

On this page

netcup API key permissions

Credential type
Legacy API key, Legacy API password, and customer number
Preview access
Legacy API Key and Legacy API Password; netcup's documented creation form has no read-only choice.
Apply access
The same Legacy API Key and Legacy API Password used for preview.
API endpoint
DNSMigrator uses the provider's fixed API endpoint.

Additional access

DNSMigrator checks the credentials by opening a CCP API session. That login check does not make a record write. The adapter calls the legacy infoDnsZone, infoDnsRecords, updateDnsZone, and updateDnsRecords methods.

DNSControl id

creds.json TYPE
{
  "TYPE": "NETCUP"
}

Create credentials

Create Legacy DNS credentials in the CCP; the current DNSMigrator adapter does not accept a CloudDNS API key.

Access you'll grant

Preview

Legacy API Key and Legacy API Password; netcup's documented creation form has no read-only choice.

Apply

The same Legacy API Key and Legacy API Password used for preview.

DNSMigrator checks the credentials by opening a CCP API session. That login check does not make a record write. The adapter calls the legacy infoDnsZone, infoDnsRecords, updateDnsZone, and updateDnsRecords methods.

Before you start

  • A netcup customer account with a domain using netcup nameservers.
  • The domain must show the DNS tab, not the CloudDNS tab, in the Customer Control Panel.

Setup steps

0 of 5 done

  1. Confirm the domain uses Legacy DNS

    In the CCP, open Domains, select the magnifying glass icon beside the domain, and look for the DNS tab. Stop if you see CloudDNS instead: CloudDNS uses a different API key that this connection does not accept.

  2. Open the API page

    In the CCP, go to Master Data → API, then find the Legacy API Keys section.

  3. Create a Legacy API key

    In Legacy API Keys, select Creating an API Key, accept the API Terms of Use, and select Confirm. Copy the generated Legacy API Key.

    Credential typeLegacy API Key
  4. Generate the Legacy API password

    In Legacy API Keys, select Regenerating API Password, accept the terms, and select Confirm. Copy the password from the confirmation before selecting Close; netcup displays it once, and regenerating it invalidates the previous password for the account.

    Credential typeLegacy API Password
  5. Paste the three values

    Paste your numeric netcup customer number into Customer number, the Legacy API Key into API key, and the one-time Legacy API Password into API password.

Troubleshooting

Login fails with credentials that work for CloudDNS

This adapter uses netcup's Legacy DNS API. Use a Legacy API Key and Legacy API Password from the Legacy API Keys section; a CloudDNS API Key is not interchangeable.

The API password no longer works

Only one Legacy API Password is assigned per customer account. If it was regenerated, update this connection with the newly displayed password.

The domain cannot be found

Confirm the domain uses netcup nameservers and the DNS tab. Non-reseller accounts cannot list all domains through listallDomains, so enter the zone name when prompted after connecting.

Official documentation

Guide checked against the official documentation on .

Credential fields

FieldRequirementWhere to find it
Customer numbercustomerNumberRequiredYour numeric netcup customer number, sent as customernumber when DNSMigrator opens the CCP API session.
API keyapiKeyRequiredThe value listed in CCP → Master Data → API → Legacy API Keys, not a CloudDNS API Key.
API passwordapiPasswordRequiredThe one-time value shown after Regenerating API Password in the Legacy API Keys section.

Capabilities

Create zones
No
List zones
No
DNSSEC
Managed through the API
Minimum TTL
86400 seconds
Apex CNAME
No
Read only
No

Record types

  • A
  • AAAA
  • CNAME
  • MX
  • TXT
  • SRV
  • CAA
  • TLSA

Caveats

  • netcup has no per-record TTL: every record uses the zone TTL (86400 seconds by default), so source TTLs are not kept.
  • Domains can only be listed for reseller accounts; everyone else enters the zone name, and NS records are not managed.
  • TXT values with quotes or backslashes and CAA values with semicolons are altered or rejected by the API.

Troubleshooting

Login fails with credentials that work for CloudDNS
This adapter uses netcup's Legacy DNS API. Use a Legacy API Key and Legacy API Password from the Legacy API Keys section; a CloudDNS API Key is not interchangeable.
The API password no longer works
Only one Legacy API Password is assigned per customer account. If it was regenerated, update this connection with the newly displayed password.
The domain cannot be found
Confirm the domain uses netcup nameservers and the DNS tab. Non-reseller accounts cannot list all domains through listallDomains, so enter the zone name when prompted after connecting.