Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Namecheap DNS
Manage Namecheap DNS records safely by fetching existing entries, merging changes, auto-backing up, previewing diffs, dry-running, and rolling back updates.
skill openclawclawhub Free
Manage Namecheap DNS records safely by fetching existing entries, merging changes, auto-backing up, previewing diffs, dry-running, and rolling back updates.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, SKILL.md, namecheap-dns.js, package-lock.json, package.json
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.1.0
Provenance
- Publisher
- jarekbird
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Namecheap DNS Management
Safe wrapper around the Namecheap API for DNS operations. Prevents accidental record wipeout by always fetching existing records first and merging changes.
โ ๏ธ Why This Skill Exists
The Namecheap API's setHosts method replaces ALL DNS records for a domain. One wrong API call = your entire DNS config is gone. This skill: โ Always fetches existing records first โ Merges new records with existing ones (unless explicitly replacing) โ Shows a diff preview before applying changes โ Auto-backups before every change โ Supports dry-run mode for safe testing โ One-command rollback from backups
1. Install dependencies
cd ~/.openclaw/workspace/skills/namecheap-dns npm install
2. Enable Namecheap API access
Go to https://ap.www.namecheap.com/settings/tools/apiaccess/ Toggle "API Access" ON Whitelist your IP address Copy your API key
3. Set environment variables
Add to ~/.zshrc or ~/.bashrc: export NAMECHEAP_API_KEY="your-api-key-here" export NAMECHEAP_USERNAME="your-username" export NAMECHEAP_API_USER="your-username" # Usually same as username
Verify DNS and detect ghost records
โ ๏ธ IMPORTANT: Run this first! ./namecheap-dns.js verify example.com This command compares DNS records visible to the Namecheap API with actual live DNS records (via dig). It will warn you about "ghost records" that exist in DNS but are invisible to the API (email forwarding, URL redirects, etc.).
List current DNS records
./namecheap-dns.js list example.com Note: This only shows records visible to the API. Use verify to see ALL records including those managed by Namecheap subsystems.
Add records (safe merge)
# Add a single TXT record ./namecheap-dns.js add example.com \ --txt "mail.example.com=v=spf1 include:mailgun.org ~all" # Add multiple records at once ./namecheap-dns.js add example.com \ --txt "mail=v=spf1 include:mailgun.org ~all" \ --cname "email.mail=mailgun.org" \ --mx "mail=10 mxa.mailgun.org" # Dry-run (preview changes without applying) ./namecheap-dns.js add example.com \ --txt "test=hello" \ --dry-run # Force override safety check (if you know ghost records can be deleted) ./namecheap-dns.js add example.com \ --txt "test=hello" \ --force Safety: The skill automatically checks for "ghost records" before making changes. If detected, it will refuse to proceed unless you use --force.
Remove records
# Remove by host + type ./namecheap-dns.js remove example.com \ --host "old-record" \ --type "TXT" # Dry-run first ./namecheap-dns.js remove example.com \ --host "old-record" \ --type "TXT" \ --dry-run
Backup & Restore
# Create manual backup ./namecheap-dns.js backup example.com # List available backups ./namecheap-dns.js backups example.com # Restore from latest backup ./namecheap-dns.js restore example.com # Restore from specific backup ./namecheap-dns.js restore example.com \ --backup "example.com-20260213-114500.json"
TXT Records
--txt "subdomain=value" --txt "@=value" # Root domain
CNAME Records
--cname "subdomain=target.com"
MX Records
--mx "subdomain=10 mx.target.com" --mx "@=10 mx.target.com" # Root domain
A Records
--a "subdomain=192.168.1.1" --a "@=192.168.1.1" # Root domain
Backup Location
Default: ./backups/ (relative to skill directory) Configurable via environment variable: export NAMECHEAP_BACKUP_DIR="/custom/path/to/backups" Format: {domain}-{timestamp}.json Each backup includes: apiHosts: Records visible to Namecheap API liveDNS: Actual DNS records captured via dig Timestamp and domain metadata This allows you to see what was ACTUALLY live in DNS, not just what the API knew about.
Safety Features
Ghost record detection โ automatic check for records invisible to API Auto-backup before changes โ every add or remove creates a timestamped backup (includes DNS snapshot) Dry-run mode โ --dry-run shows what will change without applying Diff preview โ see exactly what records will be added/removed Fetch-first โ always gets current DNS state before changes Merge logic โ adds to existing records instead of replacing Rollback โ one command to restore from backup Safety override โ --force flag for when you need to bypass ghost record warnings
Mailgun Setup
./namecheap-dns.js add menuhq.ai \ --txt "mail.menuhq.ai=v=spf1 include:mailgun.org ~all" \ --txt "smtp._domainkey.mail.menuhq.ai=k=rsa; p=MIGfMA0..." \ --txt "_dmarc.mail.menuhq.ai=v=DMARC1; p=quarantine;" \ --cname "email.mail.menuhq.ai=mailgun.org" \ --mx "mail.menuhq.ai=10 mxa.mailgun.org" \ --mx "mail.menuhq.ai=20 mxb.mailgun.org" \ --dry-run Review the diff, then run without --dry-run to apply.
โ ๏ธ The Namecheap API is Destructive
The Namecheap domains.dns.setHosts API method replaces ALL DNS records for a domain. There is no "add one record" or "update one record" endpoint. Every change requires: Fetch all existing records (getHosts) Modify the list Upload the entire list (setHosts) This skill handles this for you by always fetching first and merging changes.
๐ Ghost Records: The Hidden Danger
Problem: domains.dns.getHosts does NOT return all DNS records. Records managed by Namecheap subsystems are invisible to the API: Email Forwarding โ MX, SPF, and DKIM records URL Redirect โ A/CNAME records for domain parking/redirects Third-party integrations โ Records added through Namecheap's dashboard for services Since setHosts replaces all records, using the API can silently delete these hidden records.
๐ก๏ธ How This Skill Protects You
verify command โ Compares API records with actual live DNS (via dig) and warns about ghost records Automatic safety check โ Before any add, remove, or restore, the skill checks for ghost records Refuses to proceed โ If ghost records are detected, the operation is blocked (unless --force is used) Clear warnings โ Shows exactly which records will be lost if you proceed DNS snapshots in backups โ Captures actual DNS state via dig, not just API state
When to Use --force
Only use the --force flag when: You've manually verified the ghost records are no longer needed You're intentionally removing email forwarding or URL redirects You understand and accept that those records will be deleted Never use --force blindly. Always run verify first to see what will be lost.
Example: The Production Incident
This skill was created after adding Mailgun DNS records via the API wiped out Namecheap's email forwarding records. The email forwarding MX/SPF/TXT records were invisible to getHosts, so the fetch-merge-write pattern deleted them. Now, the skill would have: Detected the ghost records during verify Refused to proceed without --force Shown exactly which email forwarding records would be deleted Created a backup including the DNS snapshot
"API request failed: IP not whitelisted"
Add your current IP to https://ap.www.namecheap.com/settings/tools/apiaccess/ Check with: curl ifconfig.me
"Invalid API key"
Verify NAMECHEAP_API_KEY is set correctly Re-enable API access if needed
"Domain not found"
Ensure domain is in your Namecheap account Check spelling (case-sensitive)
API Reference
Namecheap API docs: https://www.namecheap.com/support/api/methods/domains-dns/
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
2 Docs2 Config1 Scripts
- SKILL.md
- README.md
- namecheap-dns.js
- package-lock.json
- package.json