🌐Websites under the customer’s domain

Under Administration → Domains, you connect Aurora Hive once to the provider where the domain is registered. Then you authorise the domain and press Publish. Aurora Hive sets the DNS records at the provider, sends www and the address without www to the same place, and obtains the certificate.

Supported providers are IONOS, Cloudflare, Hetzner, Netcup, INWX, DigitalOcean and GoDaddy. If the domain is somewhere else (Strato, All-Inkl and others without an interface), Aurora Hive tells you exactly which record to set by hand — and then checks by itself whether it is correct.

The wizard shows the route and the rights required for each provider. In short:

• IONOS: in the IONOS developer portal, create an API key. It consists of two parts (prefix and secret).
• Cloudflare: in your profile under API Tokens, a token with the “Edit DNS” permission for the zones concerned.
• Hetzner: in the Hetzner Console, an API token with read and write permission within the project.
• Netcup: in the customer control panel, create an API key and an API password; you also need your customer number.
• INWX: user name and password of an account, ideally a separate sub-account just for DNS.
• DigitalOcean: a personal access token with write permission.
• GoDaddy: key and secret from the developer area (production, not test).

When you save, Aurora Hive checks the access immediately. Red means: saved, but not usable — usually a key that was copied incompletely.

No. A key can often see all domains in an account, but Aurora Hive only touches the ones you have explicitly authorised. You can withdraw the authorisation at any time with “Withdraw authorisation”.

Aurora Hive never touches email records (MX, SPF, DKIM, DMARC) — not even on authorised domains. Your customer’s email carries on as before.

Yes, and you have to: Publish only becomes possible after the Dry run. For each name, the dry run shows what is in the DNS now and what would be there afterwards. Nothing is changed in the process.

If a name already has someone else’s value (the old website, for example), Aurora Hive asks before overwriting it and remembers the old value.

When publishing, Aurora Hive sets the DNS records first. It only creates the redirect and certificate once the domain really points to the server. If you get the message that the router will follow, the record at the provider is still propagating: wait a few minutes and press again.

With the connected providers, usually a few minutes. The DNS change first has to spread to the provider’s name servers; after that, Aurora Hive obtains the certificate, which takes about half a minute.

If a domain previously pointed to another address for a long time, individual internet connections may still have the old address cached for up to a day. That is normal and sorts itself out.

Yes, by hand. In the wizard, choose the option for providers without an interface. Aurora Hive then tells you exactly which record to set in your provider’s interface: type, name and value.

As soon as the record is set, Aurora Hive checks by itself whether the domain points to the server, and then creates the redirect and certificate.

Red means: the provider rejected the key, or Aurora Hive cannot see a single domain with it. The most common causes:

1. Key copied incompletely — paste it in again and press “Check”.
2. Key without write permission (Cloudflare, Hetzner, DigitalOcean) or created for the wrong zone.
3. With GoDaddy, a key from the test environment.
4. With Netcup, the customer number has been left out.

An account that suddenly turns red an hour later has usually been revoked at the provider or has expired.

With Clear away on the domain. Aurora Hive removes only the records it set itself, along with the redirect. If someone has since changed a record by hand, it stays in place — Aurora Hive does not overwrite other people’s work.