メニュー
Identify DNS server-side faults — wrong record, daemon down, port 53 filtered, or injected lookup latency. Use when hostname-based access fails or is slow while direct-IP access to the same target works.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Integration-test skill only. Invoke at the start of every troubleshooting session before other diagnostics to confirm the NIKA skill library is loaded.
Identify ACL and firewall faults from nftables or iptables rules. Use when traffic is selectively blocked by protocol or service (ARP, ICMP, HTTP, DNS, BGP, or packet-size filtering).
Reference list of signals that look suspicious but are normal testbed behavior. Consult before promoting any observation to a symptom.
Identify BGP routing faults — ASN misconfiguration, missing route advertisement, prefix hijacking, blackhole route leak. Use when reachability failures follow BGP-routed paths, BGP sessions fail to establish, or expected prefixes are missing from peers.
Parse oversized MCP tool output. When a tool returns "Output has been saved to <file>.txt" because the result exceeded Claude Code's token limit, run this skill's parser instead of re-reading the file in chunks. Covers `get_reachability` on large topologies and `service_snapshot` on labs with many published hostnames.
Identify DHCP server-side faults — service down, missing subnet declaration, spoofed gateway or DNS pushed by the server. Use when one or more hosts cannot obtain a lease, or hosts received DHCP-supplied values that look wrong.
| name | dns-fault-skill |
| description | Identify DNS server-side faults — wrong record, daemon down, port 53 filtered, or injected lookup latency. Use when hostname-based access fails or is slow while direct-IP access to the same target works. |
dns_record_error: the DNS server answers, but the record points to an IP the topology never declared.dns_service_down: the DNS daemon (named) is absent or not listening on port 53, so the server cannot answer queries.dns_port_blocked: the daemon is alive but nft/iptables drops port 53 traffic.dns_lookup_latency: a tc qdisc (netem delay or tbf) on the DNS server's egress adds large per-query latency while record/listener/firewall all look healthy./etc/resolv.conf differs from peers and the DNS server itself is healthy, exit to host-ip-skill and submit host_incorrect_dns there. That RCA is NOT owned by this skill.dhcpd.conf on the DHCP server pushes the wrong nameserver and affected hosts show that exact wrong resolver, exit to dhcp-fault-skill for dhcp_spoofed_dns.dns_service_down from query timeout alone; the timeout could be a firewall block or a qdisc delay. Check process, listener, AND firewall before naming dns_service_down.dns_lookup_latency needs the actual qdisc evidence on the DNS server's egress interface. High latency alone is not a fingerprint.