cloudflare-tunnel-dns

Validate Cloudflare Tunnel DNS inventory, credentials, and ingress mappings.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/pingqLIN/UniText --skill cloudflare-tunnel-dns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloudflare-tunnel-dns
Source: https://github.com/pingqLIN/UniText/tree/main/runtime/skills/cloudflare-tunnel-dns
Command: npx skills add https://github.com/pingqLIN/UniText --skill cloudflare-tunnel-dns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Cloudflare Tunnel DNS configuration can become misaligned between authoring source and runtime state, leading to broken health checks and exposed endpoints.

Core Features & Use Cases

  • Runtime projection for tunnel DNS inventory and health validation
  • Ingress to local ports and public endpoint reachability verification
  • Reference and governance guidance for staging vs prod tunnels

Quick Start

Provide your current tunnel IDs and health host, and generate a readiness checklist for deployment.

Frequently Asked Questions about cloudflare-tunnel-dns

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

FAQPage Schema
How do I validate Cloudflare Tunnel DNS configuration and ingress mappings?

Verify Cloudflare Tunnel DNS health routing by comparing authoring source configurations with runtime state. This process validates DNS hostnames for health endpoints and checks public endpoint reachability to report health-aligned configurations with guardrails.

What causes broken health checks and exposed endpoints in Cloudflare Tunnels?

Broken health checks and exposed endpoints in Cloudflare Tunnels occur when DNS configuration becomes misaligned between authoring source and runtime state. Validating DNS inventory and credentials files against runtime projections identifies and prevents these configuration drifts.

How do I verify public endpoint reachability for a Cloudflare Tunnel?

Verify Cloudflare Tunnel public endpoint reachability by parsing runtime projection data and comparing it against your inventory. This validates ingress mappings to local ports and confirms that DNS hostnames correctly route public traffic to your internal services.

Does this approach support governance guidance for staging versus production tunnels?

Yes, validating Cloudflare Tunnel DNS inventory provides reference and governance guidance for staging versus production tunnels. It compares authoring source with runtime state and reports health-aligned configurations with guardrails to maintain environment separation.

How do I generate a readiness checklist for Cloudflare Tunnel deployment?

Generate a Cloudflare Tunnel deployment readiness checklist by providing your current tunnel IDs and health host. The validation process assesses DNS inventory, credentials, and ingress mappings to produce a deployment readiness report.