hashicorp/run-dns-server
.github/skills/run-dns-server/SKILL.md
Guide for running a local containerized DNS server. Use this when asked to run an acceptance test or to run a test with the prefix `TestAcc`.
$ install --global
skillsauthnpx skillsauth add hashicorp/terraform-provider-dns run-dns-serverInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 7:54 AM23.4s1 file scanned
SKILL.md
- name:
- run-dns-server
- description:
- Guide for running a local containerized DNS server. Use this when asked to run an acceptance test or to run a test with the prefix `TestAcc`.
Before running any acceptance tests for the DNS provider, start a DNS server:
-
Check whether the DNS server is already alive by querying its locally-mapped port:
dig @127.0.0.1 -p 15353 +short ns.example.comExpected command output is "127.0.0.1."
-
If the DNS server is not already alive, then start the DNS server by running this command in the background:
docker run --privileged --cgroupns=host -d --tmpfs /tmp --tmpfs /run \ -v /sys/fs/cgroup:/sys/fs/cgroup:rw \ -v /etc/localtime:/etc/localtime:ro \ -v $PWD/internal/provider/testdata/named.conf.kerberos:/etc/named.conf:ro \ -p 127.0.0.1:15353:53 \ -p 127.0.0.1:15353:53/udp \ --rm --name ns --hostname ns.example.com ns -
After starting the DNS server, verify that the DNS server is alive by querying its locally-mapped port:
dig @127.0.0.1 -p 15353 +short ns.example.comExpected command output is "127.0.0.1." Display no output unless there is a problem.
-
If there is a problem, do not run the acceptance tests.
Add these environment variables to all go test commands for acceptance tests in the DNS provider:
DNS_UPDATE_SERVER=127.0.0.1DNS_UPDATE_PORT=15353
Related Skills
steipete/skill-creator
testing
VerifiedTrustedCommunity
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec). Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skill", "audit the skill".
356,423SKILL.mdUpdated Apr 13, 2026
steipete/healthcheck
testing
VerifiedTrustedCommunity
Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS).
356,423SKILL.mdUpdated Apr 13, 2026
openclaw/skill-creator
testing
VerifiedTrustedCommunity
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating against the AgentSkills spec). Triggers on phrases like "create a skill", "author a skill", "tidy up a skill", "improve this skill", "review the skill", "clean up the skill", "audit the skill".
353,662SKILL.mdUpdated Apr 10, 2026
openclaw/healthcheck
testing
VerifiedTrustedCommunity
Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS).
353,662SKILL.mdUpdated Apr 10, 2026