Internal DNS【免费下载链接】cloudflare-docsCloudflare’s documentation项目地址: https://gitcode.com/GitHub_Trending/cl/cloudflare-docsManage DNS records for your private network.Internal DNS zones pair with Gateway resolver policies.Create a ZoneUse the dashboard or API to create an internal zone.DashboardNavigate to Internal DNSClick Create ZoneEnter zone nameClick Save**After增强后26 行1.73 倍增长** markdown # Internal DNS Manage DNS records for your private network without running your own DNS servers. This simplifies operations and integrates with Cloudflare Gateway. Internal DNS zones pair with Gateway resolver policies to control DNS responses based on source IP, user identity, or domain. **Example use case:** A multi-region company creates views for London and SF. Users query api.company.internal but get different IPs based on location (London users → 10.0.1.100, SF users → 10.0.2.100). ## Create a Zone Create an internal zone that will contain your DNS records. Zones are only accessible via Gateway (not public DNS). ### Dashboard 1. Navigate to Internal DNS → Zones 2. Click **Create Zone** 3. Enter zone name (e.g., company.internal) 4. Click **Save** - Zone receives unique ID **Verify:** Zone appears in zone list with type internal到底加了什么逐项核对1 句解释为什么无需自建 DNS 服务器——1 行解析器策略的简要背景source IP、user identity——1 行1 个具体示例——3 行区域简要说明——2 行步骤行内上下文2 个步骤各 1 行——2 行简要验证——1 行合计原文 15 行 新增 11 行 26 行1.73 倍✅明确没有加的内容没有新增Internal DNS 解决什么问题章节、没有工作原理概念前置章节、没有图表注释、没有大段排障内容、没有完整测试章节、没有最佳实践章节、没有独立的理解 Zones章节。为什么有效完全保留原结构在读者需要的地方行内补充上下文用 1 个具体示例提供落点简短的验证帮助读者确认成功整体聚焦、可扫读。值得强调的是Pattern 0 的示例并非虚构——仓库中确实存在对应的 Internal DNS 文档见 src/content/docs/dns/internal-dns/index.mdx并且该技能目录下存放了一份完整的 ELI5 应用产物示例 index.eli5.mdx。这份示例将 overview 页从 135 行扩展到 255 行1.89 倍行内补入了使用场景、查询流程、三个用例多区域基础设施、Zero Trust 访问控制、开发/暂存环境、入门清单同时完整保留了Description、Plan、Example等 MDX 组件和全部三张 mermaid 图。Pattern 1技术优先 → 收益优先Overview 页面Before技术优先## Product X Product X is a distributed edge computing platform utilizing V8 isolates for low-latency serverless code execution with sub-millisecond cold start performance and global anycast deployment.After收益优先## Product X Run code worldwide without managing servers. Deploy in seconds, scale automatically, and pay only for what you use. **What problem it solves:** Maintaining global infrastructure is expensive and complex. Product X runs your code in 300 cities automatically. **Perfect for:** - Applications needing fast global performance - Teams wanting to skip server management - Projects with variable traffic [Get started →]为什么有效以明确的用户价值开场问题框架制造相关性Perfect for 帮助读者自我匹配技术细节被分离出去。Pattern 2抽象概念 → 具体类比Concept 页面Before抽象## Caching Caching stores frequently accessed data in high-speed storage layers to reduce origin server load and improve response times through data locality optimization.After具体## Caching **Think of it like:** A librarys reserve desk. Popular books stay at the front desk for quick access instead of requiring trips to the distant stacks. **What it is:** Caching keeps copies of your frequently accessed files (images, CSS, JavaScript) close to users, so they load instantly instead of being fetched from your origin server every time. **Why it matters:** - Pages load 10x faster (50ms vs 500ms) - Reduces server costs (fewer origin requests) - Handles traffic spikes (serves from cache, not origin) **When to use:** Any content that doesnt change constantly—images, stylesheets, blog posts, product pages.为什么有效类比立刻建立心智模型平实语言解释建立理解收益具体可度量使用场景让内容可落地。Pattern 3纯步骤 → 情境化多路径How To 页面Before纯步骤## Enable Feature X 1. Go to Settings 2. Click Security 3. Toggle Feature X to On 4. SaveAfter情境化多路径## Enable Feature X **What this does:** Protects your site from [specific threat] by [mechanism]. **Time:** ~2 minutes **Prerequisites:** Admin access ### Via Dashboard 1. Log into your dashboard at dash.example.com 2. Select your site from the list 3. Click **Security** in the left sidebar 4. Find **Feature X** and toggle it **On** 5. Click **Save Changes** at the bottom **Note:** Changes take effect immediately. Check Analytics in 5 minutes to see it working. ### Via API details summaryShow API example/summary bash curl -X PATCH https://api.example.com/v1/settings \ -H Authorization: Bearer YOUR_TOKEN \ -d {feature_x_enabled: true}Response:{ success: true, result: {feature_x_enabled: true} }Verify It WorkedVisit your site in a new tabCheck browser DevTools → Network tabLook for [specific indicator]You should see [expected result]**为什么有效** 步骤前交代目的前置条件防止困惑UI 与 API 双路径服务不同用户验证环节建立信心。 **注意 SKILL.md 的边界** 若原文只有一条路径Dashboard 或 API应在建议中标注并请作者核实**不要自行补造缺失路径**。 ### Pattern 4字母序规格 → 用例组织Reference 页面 **Before字母序** markdown ## Headers **Cache-Control:** Controls caching behavior. Values: public, private, no-cache **Content-Type:** MIME type. Examples: text/html, application/json **Expires:** Cache expiration date. Format: HTTP-dateAfter按用途组织## Headers by Purpose ### Controlling Cache Behavior **When to use:** Make your site faster by controlling what gets cached and for how long. #### Long-Term Caching (Static Assets) **Cache-Control: public, max-age31536000** **What it does:** Caches content for 1 year **When to use:** Files that never change, like logo-v2.png or style.abc123.css with version hash in filename **Example:** http Cache-Control: public, max-age31536000, immutableResult:First visitor downloads. Next year, everyone gets the cached version instantly.Fresh Content (Blog Posts)Cache-Control: public, max-age3600What it does:Caches for 1 hourWhen to use:Content that updates occasionally—blog posts, product pagesExample:Cache-Control: public, max-age3600Result:Cached for 1 hour. After that, we check for updates.Setting Content TypeWhen to use:Tell browsers what type of content theyre receiving.[Continue pattern...]**为什么有效** 按任务而非字母组织平实语言 技术规格双层结构真实示例带预期结果When to use 提供决策指导。 ### Pattern 5代码倾倒 → 解释式递进Tutorial 页面 **Before代码倾倒** markdown ## Build X javascript addEventListener(fetch, event { event.respondWith(handleRequest(event.request)) }) async function handleRequest(request) { const url new URL(request.url) return new Response(Hello) }**After解释式递进** markdown ## Build X ### What Youll Build A working [specific thing] that [specific capability]. **Example:** short.example.com/abc → github.com/cloudflare ### Who This Is For Developers comfortable with JavaScript. No prior experience needed with [platform], but you should understand HTTP requests and JSON. ### Time: 30 minutes --- ## Step 1: Minimal Working Version Lets start with the absolute minimum—proof the concept works: javascript // Entry point: listens for incoming HTTP requests addEventListener(fetch, event { // Send request to our handler function event.respondWith(handleRequest(event.request)) }) // Handler: processes each request async function handleRequest(request) { return new Response(Hello! It works!, { headers: { content-type: text/plain } }) }What this code does:Line 2:Listens for HTTP requests to your WorkerLine 4:CallshandleRequestto process each requestLine 8-12:Returns a simple text responseTest it:Deploy this codeVisit your Workers URLYou should see: Hello! It works!Great! Your Worker is running. Now lets add real functionality...Step 2: Parse URLs[Continue building progressively with explanations...]**为什么有效** 前置明确预期解释每个代码块渐进式构建最小 → 完整每步都包含测试。 --- ## 五、三种常见转换Common Transformations ### Transform 1功能列表 → 问题/解决方案 **Before** markdown Features: - Global anycast network - Automatic scaling - Pay-per-request pricingAfter**What you get:** - **Fast everywhere:** Code runs in 300 cities, close to every user - **Auto-scaling:** Handles 10 requests or 10 million without configuration - **Cost-efficient:** Pay only when code runs, not for idle serversTransform 2术语解释 → 分层理解BeforeDDoS mitigation employs anycast architecture to distribute volumetric attacks across our edge network, utilizing L3/L4 packet inspection and L7 behavioral analysis.After**In plain language:** Stops attackers from overwhelming your site with fake traffic. **How it protects you:** We have 300 data centers. When an attack hits, we spread it across all locations—like opening thousands of doors instead of one. We also identify and block fake visitors before they reach your site. **What happens:** Your real visitors get through normally while attack traffic is filtered out automatically. details summaryFor technical users/summary Anycast distributes L3/L4 volumetric attacks across the network. L7 protection uses JS challenges and behavioral fingerprinting. [Architecture details →] /details分层结构的价值在于用details折叠技术细节让普通读者和专家读者在同一页面上各取所需——这也与 SKILL.md 中面向混合读者时使用分层披露progressive disclosure的策略吻合。Transform 3隐性前提 → 显式前置条件BeforeConfigure your A record to point to the anycast IP.AfterUpdate your DNS A record to point to Cloudflares IP address. **Whats an A record?** Its the DNS entry that tells the internet where your website lives (like an address in a phone book). **Where to find it:** In your domain registrars DNS settings (GoDaddy, Namecheap, etc.). Look for DNS Management or DNS Settings. **What to enter:** - Type: A - Name: (means your root domain) - Value: 192.0.2.1 (our IP address)精确性警示结合 SKILL.md 对抗性审查要点此类补充必须注意过度概括问题。例如 Cloudflare 实际返回的是多个 anycast IP 而非单一 IP且不同记录类型A、AAAA、CNAME、MX、TXT、NS的代理规则不同——简化时若写the IP address单数或all records全体需要核实表述是否真的普适。六、隐喻模板Metaphor Templates模式库提供了三个可套用的隐喻模板核心要求是技术近邻类比tech-adjacent、有清晰的 1:1 映射、并明确说明类比的失效边界。模板一API 解释**Think of it like:** [Familiar interface concept] An API is like a restaurant menu. It shows you: - Whats available to order (endpoints) - What details you need to provide (parameters: no onions, extra cheese) - What youll get back (response: your meal) - Pricing (rate limits, quotas) You dont need to know how the kitchen works. Just order from the menu. **Where this breaks down:** Unlike restaurants where you wait, API responses are usually instant. Also, APIs can return errors if your order is invalid.模板二安全功能解释**The threat:** [What attackers do] Attackers try to [specific attack method] which could [consequence] to your site. **How [Feature] protects you:** [Protection mechanism in plain language] Think of it like [security analogy]: [Concrete comparison that shows the protection model] **What happens automatically:** - [Protection 1] - [Protection 2] **What you control:** - [Setting 1] - [Setting 2]模板三基础设施概念**What it is:** [One-sentence plain English definition] **Real-world comparison:** [Physical/familiar tech analog that maps 1:1 to key concepts] **Why it matters:** - [Benefit 1 with measurable impact] - [Benefit 2 with measurable impact] **Common use case:** [Specific realistic scenario showing it in action] **Technical details:** [In collapsible section or bottom]【免费下载链接】cloudflare-docsCloudflare’s documentation项目地址: https://gitcode.com/GitHub_Trending/cl/cloudflare-docs创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考