원클릭으로 Manus에서 모든 스킬 실행

dns-dhcp-troubleshooter

스타424

포크54

업데이트2026년 5월 21일 03:24

Diagnose DNS and DHCP problems in KKTerm, including failed hostname lookup, wrong records, split DNS, stale cache, DHCP lease issues, gateway/DNS option problems, and VPN DNS behavior.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

ryantsai

ryantsai/KKTerm

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

DNS and DHCP Troubleshooter

Use this skill when a hostname resolves incorrectly, only works on some networks, fails after VPN changes, or the local machine has suspicious IP/gateway/DNS settings.

Workflow

Determine whether the symptom is DNS, DHCP, or both: name lookup failure, wrong address, search suffix issue, no lease, wrong gateway, or wrong DNS server.
Identify the resolver path: Windows DNS client, WSL resolver, VPN-provided DNS, remote SSH host resolver, or application-specific proxy.
Ask for the exact hostname and expected network context, but do not ask for secrets or private zone contents beyond what is needed.
Compare authoritative intent vs client result when available: expected record, actual answer, resolver used, TTL/cache behavior, and search suffix expansion.
For split DNS, check whether the user is on the right VPN or network and whether the query is being sent to the internal resolver.
For DHCP, inspect lease address, subnet mask, gateway, DNS servers, and lease age before suggesting renew/release actions.
Avoid telling users to hard-code public DNS servers when private zones, VPNs, domain controllers, or corporate policy may be required.
If flushing cache is suggested, explain that it removes cached client answers but does not fix authoritative records or resolver policy.

Command Guidance

Windows DNS: Resolve-DnsName <host>, nslookup <host>, Get-DnsClientCache, Get-DnsClientServerAddress.
Windows DHCP/interface: Get-NetIPConfiguration, ipconfig /all, ipconfig /renew only after confirming a local lease problem.
WSL/POSIX: getent hosts <host>, resolvectl query <host> when available, cat /etc/resolv.conf.
Remote SSH vantage point: run resolver checks on the remote host only when the question is about that remote network.

KKTerm Boundaries

DNS behavior can differ between local Windows terminal Sessions, WSL, SSH Sessions, and WebView2 URL Connections.
A Connection hostname is durable data, but DNS answers are runtime environment state.
Do not rewrite Connection hosts from names to IPs unless the user explicitly wants that tradeoff.

이 저장소의 다른 Skills

같은 저장소

dashboard-data-visualization

ryantsai/KKTerm

Design KKTerm Dashboard widgets that show metrics, charts, logs, timelines, gauges, health states, trends, and operational data without misleading users.

2026-06-03424

dashboard-widget-designer

ryantsai/KKTerm

Improve KKTerm Dashboard AI Created Widget visual design, layout hierarchy, desktop utility polish, design-system consistency, compact states, and redesign critique.

2026-06-03424

desktop-accessibility-ui

ryantsai/KKTerm

Review KKTerm UI and Dashboard widgets for accessible desktop usability, contrast, focus, keyboard behavior, readable text, motion restraint, and non-color status cues.

2026-06-03424

dashboard-widget-builder

ryantsai/KKTerm

Create, repair, redesign, and troubleshoot KKTerm Dashboard AI Created Widgets, script widgets, widget layout, visual polish, data fetching, secrets, and custom Dashboard views.

2026-05-28424

firewall-port-troubleshooter

ryantsai/KKTerm

Diagnose firewall, NAT, listener, and port reachability problems in KKTerm, including blocked SSH, RDP, VNC, HTTP(S), SFTP, custom ports, Windows Firewall, and remote service binding issues.

2026-05-21424

network-connectivity-troubleshooter

ryantsai/KKTerm

Diagnose general network connectivity failures in KKTerm, including unreachable hosts, routing, gateway, VPN, proxy, packet loss, latency, MTU, and local-vs-remote reachability checks.

2026-05-21424

name	dns-dhcp-troubleshooter
description	Diagnose DNS and DHCP problems in KKTerm, including failed hostname lookup, wrong records, split DNS, stale cache, DHCP lease issues, gateway/DNS option problems, and VPN DNS behavior.

DNS and DHCP Troubleshooter

Use this skill when a hostname resolves incorrectly, only works on some networks, fails after VPN changes, or the local machine has suspicious IP/gateway/DNS settings.

Workflow

Determine whether the symptom is DNS, DHCP, or both: name lookup failure, wrong address, search suffix issue, no lease, wrong gateway, or wrong DNS server.
Identify the resolver path: Windows DNS client, WSL resolver, VPN-provided DNS, remote SSH host resolver, or application-specific proxy.
Ask for the exact hostname and expected network context, but do not ask for secrets or private zone contents beyond what is needed.
Compare authoritative intent vs client result when available: expected record, actual answer, resolver used, TTL/cache behavior, and search suffix expansion.
For split DNS, check whether the user is on the right VPN or network and whether the query is being sent to the internal resolver.
For DHCP, inspect lease address, subnet mask, gateway, DNS servers, and lease age before suggesting renew/release actions.
Avoid telling users to hard-code public DNS servers when private zones, VPNs, domain controllers, or corporate policy may be required.
If flushing cache is suggested, explain that it removes cached client answers but does not fix authoritative records or resolver policy.

Command Guidance

Windows DNS: Resolve-DnsName <host>, nslookup <host>, Get-DnsClientCache, Get-DnsClientServerAddress.
Windows DHCP/interface: Get-NetIPConfiguration, ipconfig /all, ipconfig /renew only after confirming a local lease problem.
WSL/POSIX: getent hosts <host>, resolvectl query <host> when available, cat /etc/resolv.conf.
Remote SSH vantage point: run resolver checks on the remote host only when the question is about that remote network.

KKTerm Boundaries

DNS behavior can differ between local Windows terminal Sessions, WSL, SSH Sessions, and WebView2 URL Connections.
A Connection hostname is durable data, but DNS answers are runtime environment state.
Do not rewrite Connection hosts from names to IPs unless the user explicitly wants that tradeoff.