Skip to content
DNS & DynDNSUpdated: 02/11/2026

Netcup DNS setup: records, nameservers and DynDNS

From the first A record to the DynDNS update: this guide shows the order, common mistakes and how to verify every change with dig.

Tool for this guide

DNS record builder

Generates a BIND-style line for Netcup DNS or CloudDNS. Copy the record into the zone and verify it with dig.

Generated record
@	300	IN A	203.0.113.10

The trailing dot on an FQDN matters. TXT values are wrapped in quotes.

1. Preparation

Open the domain in the CCP and confirm that the Netcup nameservers are active. For external domains, use CloudDNS and set the Netcup nameservers at your registrar.

Decide which subdomain points to which IP. Use A for IPv4 and AAAA for IPv6. A CNAME must not point to the zone apex and must not conflict with other records at the same name.

  • Select the domain in the CCP and open the DNS zone.
  • Keep the TTL short for tests (e.g. 300 s), then raise it.
  • Verify changes with dig or nslookup.

2. The important records

A and AAAA connect a name to an IP. MX points to the mail server; TXT carries SPF, DKIM and DMARC. For web hosting, the A record points to the Netcup web hosting IP; for your own server, to its IP.

; Example for example.com
@       300  IN A     203.0.113.10
www     300  IN CNAME example.com.
@       300  IN MX    10 mail.example.com.
@       300  IN TXT   "v=spf1 mx -all"
_dmarc  300  IN TXT   "v=DMARC1; p=quarantine; rua=mailto:[email protected]"

Note: The trailing dot on an FQDN matters. DKIM needs an additional TXT record generated by your mail provider; copy it exactly.

3. DynDNS

DynDNS updates an A or AAAA record when your public IP changes. Netcup documents the Dynamic DNS interface; routers and servers use different update URLs and authentication methods.

Test the update by querying the record with dig and comparing it to your current WAN IP. A TTL of 300 s makes the test faster.

dig +short A home.example.com
curl -4 ifconfig.me
# Both values must match.

4. Verify and debug

Check the authoritative nameserver first, then a resolver. If the change is missing only locally, the cache or TTL is often the cause.

dig @ns1.example.com example.com A
dig example.com A
dig example.com MX
dig example.com TXT

Note: Replace ns1.example.com with the actual Netcup nameserver shown in the CCP. CloudDNS uses the nameservers shown there.

Official sources

Matching plans

VPS 1000 G12.5

Bestseller
VPS • G12.5
1 Month Free
€14.50/ moincl. 19% VAT12-month term

4 vCores (x86) · 8 GB RAM · 128 GB SSD · 2.5 Gbit/s

GB6: 1,720/4,650 · Steal: 1.2 %

Loading current code…

RS 1000 G12.5

Bestseller
Root server • G12.5
2 Months Free
€21.73/ moincl. 19% VAT12-month term

4 Dedicated Cores (AMD EPYC 9645) · 8 GB RAM · 128 GB NVMe · 2.5 Gbit/s

GB6: 2,290/7,559 · Steal: 0.0 %

Loading current code…
Webhosting • 2026
30% Monthly Discount
€4.03/ moincl. 19% VAT12-month term

Shared Webhosting Cluster · 4 GB RAM · 150 GB SSD (3 Free Domains) · 1 Gbit/s

No benchmark data

Loading current code…

Frequently asked questions

Which nameservers should I use?

The nameservers Netcup shows in the CCP for the domain. For external domains with CloudDNS, use the CloudDNS nameservers. Only change them if you really want to move DNS management.

How long does DNS propagation take?

It depends on the TTL and resolver caches. With a 300 s TTL, changes often appear within minutes; old caches can last longer. Check authoritative and public resolvers.

Can I put Cloudflare in front of Netcup?

Yes, you can change the nameservers at your registrar to Cloudflare. Cloudflare then manages the zone, not Netcup. Check DNSSEC and mail records before switching.

Does the €5 voucher apply to domains?

No. Vouchers do not apply to domains, VPS ARM, VPS Lite and merchandise. The DNS guide is independent of the domain order.