Dotnify · Domain and Server IP Management (Personal Extension)

This personal edition of Dotnify is for developers maintaining several domains and servers. It brings three questions into one management area: what a server is, which domains point to it, and what has changed recently. Built on the open-source airtouch97/Dotnify project, it extends the original domain and DNS record management with a named server IP register, usage inventories, change restoration, and assistant operations.

Connect server identities with domain records

• A named server register: Server entries can have recognizable names and notes and can be maintained as addresses change, reducing reliance on an address alone to identify its purpose.
• Inventory and search by destination: For an inventory, the tool checks address records for connected domains and groups hostnames that point to the same IP. Users can search by address, server name, or hostname, and focus on addresses with more associated records.

Progress is shown, and domains that could not be read are listed separately for follow-up, so partial results are not mistaken for a complete asset inventory.

Confirm the target before changing its destination

Before changing a domain’s destination, the user can inspect its current records, then bind a hostname to a named server or give a new address a name. The assistant extension can also query, bind, and unbind records and preview changes before execution. The server register and live DNS records serve separate purposes: changing an address in the register does not automatically rewrite existing DNS records, so a migration still requires checking the relevant domains.

Restore a change and follow its history

1. Inspect the recorded change: Recorded changes show their time, operation source, result, and before-and-after differences.
2. Request restoration and check for conflicts: If an operation needs to be reversed, the user can initiate restoration from its record. If the target was subsequently changed or deleted, or a conflict exists, the tool explains the current situation and requires further confirmation.
3. Keep a restoration record: Restoration creates its own record, allowing the original change and its reversal to be followed together rather than showing only the final state.

Notifications and operation scope

Changes can also trigger email according to configuration, with delivery success or failure shown in history. This helps the user follow changes away from the management page. The personal extensions focus on recognizable server names, inspectable history, and traceable restoration. Operations are limited to connected domains and the available permissions, and scan results should be read alongside any failures.