Skip to content
Skills Library
DevOps & cloud · Analysis

dns-tools

/dns-tools

DNS resolution and propagation debugging. Use when looking up A/AAAA/MX/TXT records, verifying DNS changes across resolvers, or querying via DoT/DoH.

Licence
MIT
Last repository change
24.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
3
Deprecation

No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

DNS resolution and propagation debugging. Use when looking up A/AAAA/MX/TXT records, verifying DNS changes across resolvers, or querying via DoT/DoH.

Original author description

DNS resolution and propagation debugging. Use when looking up A/AAAA/MX/TXT records, verifying DNS changes across resolvers, or querying via DoT/DoH.

How it works

  1. When to Use This Skill
  2. Core Expertise
  3. Essential Commands
  4. DNS-over-TLS and DNS-over-HTTPS
  5. Advanced Features
  6. Common Patterns
  7. Alternative Tools
  8. Agentic Optimizations
  9. Quick Reference
  10. Error Handling
Original SKILL.md headings · 274 lines, 1,057 words
SKILL.md preview
---
name: dns-tools
description: DNS resolution and propagation debugging. Use when looking up A/AAAA/MX/TXT records, verifying DNS changes across resolvers, or querying via DoT/DoH.
user-invocable: false
allowed-tools: Bash(dog *), Bash(dig *), Bash(drill *), Read, Grep, Glob, TodoWrite
created: 2026-01-01
modified: 2026-10-12
reviewed: 2026-04-25
---

# DNS Tools

## When to Use This Skill

| Scenario | Use this skill | Alternative |
|----------|---------------|-------------|
| Look up DNS records (A, MX, TXT, etc.) | Yes | |
| Check DNS propagation across resolvers | Yes | |
| Query via encrypted DNS (DoT/DoH) | Yes | |
| Verify email auth records (SPF/DKIM/DMARC) | Yes | |
| Reverse DNS lookup for an IP | Yes | |
| Troubleshoot connectivity or packet loss | | network-diagnostics (trippy, gping) |
| Find hosts or open ports on a network | | network-discovery (RustScan, nmap) |
| Discover devices on local L2 segment | | layer2-discovery (ARP/LLDP) |
| Load test an HTTP endpoint | | http-load-testing (oha) |
| Monitor real-time bandwidth per process | | network-monitoring (bandwhich) |
| Inspect or configure the host's own IPs, links, or routes | | interface-state (ip) |

## Core Expertise

**dog** is a modern, Rust-based DNS client that serves as a user-friendly alternative to `dig`. Key advantages:

- **Readable output**: Colorized, human-friendly formatting by default
- **Modern protocols**: Native support for DNS-over-TLS (DoT) and DNS-over-HTTPS (DoH)
- **JSON output**: Machine-parseable output for scripting and automation
- **Fast**: Compiled Rust binary with minimal dependencies
- **Cross-platform**: Works on Linux, macOS, and Windows

### Installation

```bash
# macOS
brew install dog

# Cargo (any platform)
cargo install dog

# Arch Linux
pacman -S dog
```

## Essential Commands

### Basic Queries

```bash
# Query A record (default)
dog example.com

# Query specific record type
dog example.com MX
dog example.com AAAA
dog example.com TXT

# Query multiple record types
dog example.com A AAAA MX

# Query multiple domains
dog example.com example.org
```

### Specifying DNS Server

```bash
# Use specific resolver
dog @8.8.8.8 example.com
dog @1.1.1.1 example.com MX

# Use system resolver explicitly
dog @/etc/resolv.conf example.com
```

### Output Formats

```bash
# JSON output for parsing
dog --json example.com

# Short output (answers only)
dog --short example.com

# Quiet mode (minimal output)
dog -q example.com
```

## DNS-over-TLS and DNS-over-HTTPS

Modern encrypted DNS protocols prevent eavesdropping and tampering.

### DNS-over-TLS (DoT)

```bash
# Query via DoT (port 853)
dog --tls @dns.google example.com
dog --tls @1.1.1.1 example.com

# Explicit TLS server specification
dog --tls @dns.quad9.net example.com
```

### DNS-over-HTTPS (DoH)

```bash
# Query via DoH
dog --https @https://dns.google/dns-query example.com
dog --https @https://cloudflare-dns.com/dns-query example.com

# Quad9 DoH
dog --https @https://dns.quad9.net/dns-query example.com
```

### Protocol Comparison

| Protocol | Flag | Port | Use Case |
|----------|------|------|----------|
| UDP | (default) | 53 | Standard queries |
| TCP | `--tcp` | 53 | Large responses, reliability |
| DoT | `--tls` | 853 | Encrypted, TLS-based |
| DoH | `--https` | 443 | Encrypted, HTTPS-based |

## Advanced Features

### Query Options

```bash
# Force TCP instead of UDP
dog --tcp example.com

# Set query timeout (seconds)
dog --timeout 5 example.com

# Disable recursion (query authoritative only)
dog --no-recurse example.com

# Query specific class
dog --class CH version.bind TXT  # Chaos class for version info
```

### Reverse DNS

```bash
# PTR lookup for IP address
dog -x 8.8.8.8
dog --reverse 1.1.1.1
```

### DNSSEC Queries

```bash
# Request DNSSEC records
dog --dnssec example.com

# Query DNSKEY records directly
dog example.com DNSKEY
dog example.com DS
```

## Common Patterns

### Troubleshooting DNS

```bash
# Check propagation across multiple resolvers
dog @8.8.8.8 example.com A
dog @1.1.1.1 example.com A
dog @9.9.9.9 example.com A

# Verify MX records for email
dog example.com MX --json | jq '.answers[].data'

# Check SPF/DKIM/DMARC for email auth
dog example.com TXT | grep -E 'spf|dkim|dmarc'
dog _dmarc.example.com TXT
dog selector._domainkey.example.com TXT
```

### Automation and Scripting

```bash
# Extract IP addresses from JSON
dog --json example.com A | jq -r '.answers[].data'

# Check if domain resolves
dog --short example.com && echo "Resolves" || echo "No resolution"

# Batch queries
for domain in example.com example.org; do
  dog --json "$domain" A
done
```

## Alternative Tools

### dig (Traditional)

Still valuable for DNSSEC validation and advanced debugging:

```bash
# DNSSEC validation
dig +dnssec example.com

# Trace delegation path
dig +trace example.com

# Query with specific options
dig +noall +answer example.com MX
```

### drill (LDNS Project)

DNSSEC-focused tool from NLnet Labs:

```bash
# DNSSEC chase
drill -S example.com

# Trace from root
drill -T example.com
```

## Agentic Optimizations

| Context | Command |
|---------|---------|
| Parse results | `dog --json example.com` |
| Quick check | `dog --short example.com` |
| Minimal output | `dog -q example.com A` |
| Extract IPs | `dog --json example.com A \| jq -r '.answers[].data'` |
| Batch queries | Loop with `--json` for structured output |
| CI/CD checks | `dog --json --timeout 5` for fast, parseable results |

## Quick Reference

### Record Types

| Type | Description | Example |
|------|-------------|---------|
| A | IPv4 address | `dog example.com A` |
| AAAA | IPv6 address | `dog example.com AAAA` |
| MX | Mail exchanger | `dog example.com MX` |
| NS | Name server | `dog example.com NS` |
| TXT | Text record | `dog example.com TXT` |
| CNAME | Canonical name | `dog www.example.com CNAME` |
| SOA | Start of authority | `dog example.com SOA` |
| PTR | Pointer (reverse) | `dog -x 8.8.8.8` |
| SRV | Service record | `dog _sip._tcp.example.com SRV` |
| CAA | Certificate authority | `dog example.com CAA` |

### Common Flags

| Flag | Short | Description |
|------|-------|-------------|
| `--json` | `-J` | JSON output |
| `--short` | `-s` | Answers only |
| `--tcp` | `-T` | Use TCP |
| `--tls` | | DNS-over-TLS |
| `--https` | `-H` | DNS-over-HTTPS |
| `--reverse` | `-x` | Reverse lookup |
| `--timeout` | | Query timeout |
| `--dnssec` | `-D` | Request DNSSEC |
| `--class` | `-C` | Query class |
| `--no-recurse` | | Disable recursion |

## Error Handling

| Error | Cause | Solution |
|-------|-------|----------|
| NXDOMAIN | Domain does not exist | Verify domain spelling |
| SERVFAIL | Server failure | Try different resolver |
| REFUSED | Query refused | Server policy, try public resolver |
| Timeout | No response | Check network, increase `--timeout` |
| Connection refused | DoT/DoH server unreachable | Verify server address and port |

Versions

The database has no other skills named dns-tools.

Database snapshot: 13.11.2026 · package version 66137d52d87f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100dns-architecture-resolution-records
    Use this skill when troubleshooting DNS recursive queries, TTL caching, split-horizon DNS, and A/AAAA/CNAME/TXT/MX records.
  • 100dns
    Cross-platform comparison and architecture guidance for all DNS technologies: authoritative vs recursive DNS, zone types, DNSSEC, DoH/DoT, DNS security (RPZ, DNS firewall), and hybrid DNS architecture. Use for \"DNS\", \"name resolution\", \"DNSSEC\", \"zone transfer\", \"DNS…
  • 100dns-record-analyzer
    Audits and troubleshoots DNS records for domains including A, AAAA, CNAME, MX, TXT, SPF, DKIM, DMARC, CAA, and NS records. Use when someone needs to verify DNS configuration, debug DNS propagation issues, check email authentication records, or audit domain security. Trigger…
  • 100dns-operations
    Use when managing on-premises DNS infrastructure — editing BIND zone files, adding or removing DNS records (A, AAAA, CNAME, MX, TXT, PTR), debugging DNS resolution failures, managing reverse DNS zones, or verifying DNS propagation. Also use for "add DNS record", "fix DNS", "zone…
  • 100namecheap
    Manage DNS records for domains registered with Namecheap via their API. List domains, view/add/update/remove DNS host entries (A, AAAA, CNAME, MX, TXT, etc.), and guide users through API setup including public IP detection and credential configuration. Use when the user mentions…
  • 100dns-management
    Configure DNS zones and records. Manage Route53, Cloud DNS, and self-hosted DNS. Use when setting up DNS infrastructure.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.