agentleFS
lordmaculordmacu/nexo-rs/skills/dns-tools/SKILL.md

DNS Tools

Skill8 starsChanged 7 months agoApache-2.0View on GitHub

Resolve DNS records (A, AAAA, MX, TXT, CNAME, NS, SOA, SRV, CAA), PTR reverse, and WHOIS.

The file

Files
SKILL.md

DNS Tools

Low-level DNS lookups and WHOIS. Backed by the dns-tools extension using hickory-resolver (pure Rust, no dig binary).

Use when

  • "What's the A/MX/TXT/NS record for domain.tld?"
  • "Reverse lookup 1.2.3.4"
  • "Who owns this domain?" (WHOIS)
  • Verifying DNS propagation after a Cloudflare change

Do not use when

  • Modifying records — use cloudflare (or the relevant provider skill)
  • Deep port scans or HTTP probing — use endpoint-check / fetch-url

Tools

  • status — resolver info
  • resolve — name + optional type (A default). Supports A/AAAA/CNAME/MX/TXT/NS/SOA/SRV/CAA
  • reverse — ip → PTR names
  • whois — domain; queries whois.iana.org then follows referral to the TLD server

Notes

  • Resolver reads /etc/resolv.conf; falls back to Cloudflare 1.1.1.1 if missing
  • WHOIS body is truncated at 8 KB

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.