Delegation
A change of NS servers is filed with the registry by the provider. Propagation across the global DNS takes up to 24 hours.
Service
Record management stays with the client: values are edited in the panel, validated before saving and stored with a version history. Changing NS servers in the registry is handled by the provider.
01Record types
Values are validated before saving, so an invalid record never reaches the zone.
02How it works
The client shapes the contents of the zone, the provider handles the registry side.
A change of NS servers is filed with the registry by the provider. Propagation across the global DNS takes up to 24 hours.
A, AAAA, CNAME, MX, TXT and CAA records are changed by the client without any approval.
The format of a record is checked before saving: a syntax error never reaches the published zone.
Every edit is stored with its date and author, and a previous version of the zone can be restored.
When a project moves, the records are prepared in advance and switched over at an agreed time.
The provider gets no access to the website, email or content of the project.
03About the service
The questions that come up most often when moving a project or setting up email.
Ask a questionThe values come from the client and the request is filed with the registry by the provider. Propagation across the global DNS takes up to 24 hours.
No. Records inside the zone are changed by the client. Approval is only needed for a change of delegation.
The format is validated before saving. If a faulty record does get published, the previous version of the zone is restored from the change history.
Yes. It is enough to set the NS servers of the chosen provider; the zone is then managed on their side.
04Contacts
Describe the task: a hosting move, email setup or connecting an external service.