1. Analyze the Request:

    • Source Language: zh-cn (Simplified Chinese).
    • Target Language: it-it (Italian).
    • Content: A Markdown blog post about securing public IPv6 usage.
    • Role: Professional localization translation expert.
    • Constraints:
      • Keep formatting (Markdown, code blocks, front matter).
      • Keep technical terms/API names unchanged (e.g., “tailscale”, “zerotier”, “IPv6”, “DNS”, “AAAA”, “nginx”, “IIS”, “127.0.0.1”, “::1”, “0.0.0.0”, “403”, “AdGuardHome”, “AdGuardPrivate”, “dnspod.cn”).
      • No explanations, No extra content, No whitespace changes.
      • Triple backticks count must match.
      • Specific user instruction: Markdown front matter tags, category, description need translation; slug does not (no slug present, but categories and tags are).
      • Logic: Check if translation is needed (Yes, it’s a document with natural language).

  2. Analyze the Source Content:

    • Front Matter:
      • layout: blog (Keep)
      • categories: 网络 -> Translate “网络” to Italian (e.g., “Rete”, “Networking”). Let’s use “Rete” or “Network”. Given the context, “Rete” or “Networking” works. I’ll use “Networking” or “Rete”. “Rete” is simpler, “Networking” is more technical. Let’s go with “Rete” as a category or “Reti”. Actually, “Network” is often used untranslated in tech blogs, but since the prompt asks for translation, I’ll translate it. “Rete” (singular) or “Reti” (plural). The value is singular “网络”, so “Rete”.
      • tags: [网络, 网络] -> Translate “网络”. Usually tags might be English even in Italian blogs, but instruction says translate. So ["Rete", "Rete"].
      • draft: false (Keep)
      • title: 几个更安全使用公网IPv6的方法 -> “Alcuni metodi per un uso più sicuro dell’IPv6 pubblico”.
      • date: ... (Keep)
      • comments: true (Keep)
      • giscus_comments: true (Keep)
      • description: (Empty in source, keep empty)
      • weight: 100 (Keep)
    • Body:
      • Intro: Using public IPv6 to connect home vs VPN (tailscale/zerotier). Cell phones have IPv6.
      • Reference to previous article: V2EX link.
      • ISP pitfall: Domain scanning exposes IPv6, leads to service degradation.
      • “Cyberspace scanning” (网络空间扫描): Scans IP pools directly.
      • List of scanning types (IP liveness, Port/Service, OS, Traffic, Alias, DNS).
      • Solutions:
        1. Internal DNS doesn’t return AAAA.
        2. Internal services only via domain, not IP.
        3. Use private DNS (AdGuardPrivate).
      • Section 1: DNS server no AAAA. Browsing exposes IPv6. Sacrifice outgoing IPv6, keep for incoming. AdGuardHome config screenshot ref.
      • Section 2: Service only via domain. Don’t listen on 0.0.0.0 or ::. Nginx example code. IIS example screenshot.
      • Section 3: Private DNS service. Fake domain pointing to internal service. Benefits: save money, hard to scan.
      • Mermaid diagram: Translate labels (“Scanner”, “DNS”, “Service”, steps, notes).
      • Comparison: AdGuardPrivate vs dnspod.
      • Summary: Recap points.
      • Conclusion: Tailscale/zerotier are best/easiest but sometimes fail. Don’t use random Wi-Fi. Joke about traffic card.

  3. Drafting the Translation (Iterative Refinement):

    • Front Matter:

      • categories: 网络 -> categories: Rete
      • tags: [网络, 网络] -> tags: [Rete, Rete]
      • title: 几个更安全使用公网IPv6的方法 -> title: Alcuni metodi per un uso più sicuro dell'IPv6 pubblico

    • Intro:

      • “有些人会有使用公网 IPv6 回家的需求…” -> “Alcuni potrebbero avere la necessità di utilizzare l’IPv6 pubblico per rientrare a casa (connettersi alla rete domestica), a differenza di VPN come tailscale/zerotier che richiedono il NAT traversal o hole punching per stabilire una connessione diretta, l’IPv6 è una connessione diretta; la rete cellulare dei telefoni ha l’IPv6 la maggior parte del tempo, rendendo molto comodo il rientro a casa.”
      • “我之前分享过一篇文章…” -> “In precedenza ho condiviso un articolo [L’utilizzo di sottodomini DDNS comuni per