dns

Diagnoses and configures DNS resolution using dig, nslookup, and host.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/ryukyagamilight/terminal-skills --skill dns-ryukyagamilight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dns
Source: https://github.com/ryukyagamilight/terminal-skills/tree/main/network/dns
Command: npx skills add https://github.com/ryukyagamilight/terminal-skills --skill dns-ryukyagamilight

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the complex tasks of configuring, troubleshooting, and understanding DNS resolution, including popular tools like BIND and CoreDNS.

Core Features & Use Cases

  • DNS Query Tools: Utilize dig, nslookup, and host for detailed DNS lookups.
  • Local Configuration: Manage /etc/resolv.conf, /etc/hosts, and systemd-resolved.
  • Server Management: Configure and troubleshoot BIND and CoreDNS servers.
  • Use Case: Quickly diagnose why a new internal service is not accessible by using dig to trace the DNS resolution path and checking local configuration files.

Quick Start

Use the dns skill to troubleshoot a DNS resolution issue for 'example.com'.

Frequently Asked Questions about dns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot DNS resolution issues for a specific domain?

Troubleshoot DNS resolution by using tools like dig, nslookup, and host to trace the query path. Check local configuration files such as /etc/resolv.conf and /etc/hosts, or verify systemd-resolved status to identify where the lookup fails.

What is the best way to configure a local DNS resolver on Linux?

Configure local DNS resolution by editing /etc/resolv.conf to set nameservers or modifying /etc/hosts for static overrides. Use systemd-resolved to manage network-specific configurations and ensure local queries route correctly.

How does CoreDNS compare to BIND for internal DNS server setups?

CoreDNS and BIND are both supported for server management, but CoreDNS is lightweight and dynamic, while BIND offers robust, traditional configuration. Choose CoreDNS for containerized environments or BIND for enterprise-scale zone management.

Why is my new internal service not accessible via DNS?

Your internal service is likely inaccessible due to missing DNS records or local resolver caching. Use dig to trace the DNS resolution path, verify the server configuration in BIND or CoreDNS, and clear local caches.

Can I manage systemd-resolved configurations for DNS troubleshooting?

Yes, you can manage systemd-resolved to control local DNS settings. Modify its configuration to update resolver behavior, check its status for active connections, and ensure it properly forwards queries to your target DNS servers.

What are the limitations of using /etc/hosts for DNS resolution?

Using /etc/hosts for DNS resolution limits you to static, local-only overrides without wildcard support or caching. It cannot handle dynamic network environments or scale for enterprise zones, making it unsuitable for complex DNS configurations.