Domains, DNS, hosting and email from a single source.
Resources & Support



The delegation carries your name, not ours.
Your zones answer under ns1.yourcompany.com instead of our address. Behind it sits the same anycast network with the same locations. The delegation carries your name. The addresses behind it stay our anycast network.
Running domains for other people means leaving your supplier’s name behind on every lookup. That is not cosmetic: your client sees in WHOIS, in every DNS check and in every competitor’s migration pitch who actually does the work.
Here it belongs to the Business plan: no enterprise contract, no minimum commitment, no sales call. And the way out stays open, with or without a plan.
Set up once
We create the IP addresses and the glue records so nothing goes wrong by hand.
Three names per set, for example ns1 to ns3. The domain carrying them has to be in your regfish account with its zone here, because that is where we write the glue records.
The addresses of our anycast network and the glue records at the registry are set automatically. That is the step we take off your hands.
One click per domain. One set carries any number of zones, so you do not need one per client, and over the API the switch runs as a loop across your domains.
Three paths, one result
Moving a hundred client domains should not mean a hundred clicks.
dash.regfish.de /my /vanity-nsCreate sets, assign names and move domains onto a set one at a time.
GET /PUT /domains /{domain} /nameserversThe GET lists your account’s sets and the current delegation, the PUT moves a domain onto a set or back. Free-form nameservers are deliberately refused.
MCP: update_nameserversAn agent can drive the migration, but it still runs into your guard rules.
Nothing left out
The limits are stated here, not discovered in the interface.
One plan per account, unlimited domains. Working for forty clients costs the same as working for four.
Before you ask
Opening an account is free. A set takes a few minutes; we handle the glue records.