domainion-ops

What This Skill Does

Domainion Ops is a comprehensive AI-driven skill designed for OpenClaw agents to manage domain registration and DNS operations programmatically. It abstracts the complexity of interacting with multiple domain registrars by providing a unified interface for name.com (default), GoDaddy, and Namecheap. The skill handles the full lifecycle of domain management, including checking domain availability, registering new domains, managing complex DNS records (A, AAAA, CNAME, MX, TXT, NS, SRV), performing nameserver flips, and executing DNS propagation verification. It ensures operational safety by requiring credential verification for each provider before execution and enforces robust guardrails, such as performing ID-checks before destructive actions like record deletion or nameserver updates.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/iahmadzain/domainion-ops. Once installed, ensure you have configured your credentials for the desired providers in your environment variables or the ~/.domainion file. Missing credentials will trigger an automated request for you to supply them before any network-dependent action is permitted.

Use Cases

This skill is ideal for DevOps engineers and site administrators who need to manage multi-vendor infrastructure. Use it to automate the rapid deployment of DNS records when standing up new web applications, manage bulk domain renewals to prevent accidental expirations, or flip nameservers during migration projects. It is also excellent for technical troubleshooting, such as verifying global DNS propagation after a site migration or confirming that MX records for email services are configured correctly across different registrars.

Example Prompts

1. "Check if cloud-platform-v2.com is available on GoDaddy and let me know the cost."
2. "Add an A record for dev.mysite.com pointing to 192.168.1.50 using my Namecheap account."
3. "Verify if the DNS changes for example.com have fully propagated to the global nameservers."

Tips & Limitations

To ensure success, always follow the TTL strategy: lower your TTL to 300 seconds at least one cycle before implementing a significant change, then restore it to 3600 once changes are verified. Never attempt to lower the TTL after the change has already been pushed, as it will be ineffective. Because this skill interacts with live registrar APIs, it is subject to the rate limits and API availability of the respective provider. Always confirm the registrar and domain name before running destructive commands. If the agent does not specify a provider, it will default to name.com, so be explicit if your domain resides elsewhere.