← 返回
安全合规
中文
DNS
Configure DNS records correctly with proper TTLs, email authentication, and migration strategies.
正确配置DNS记录,包括TTL设置、邮件认证及迁移策略。
ivangdavila
安全合规
clawhub
v1.0.0 1 版本 99718.3 Key: 无需
#latest
概述
Pre-Migration TTL
- Lower TTL to 300s at least 48h before changing records—current TTL must expire first
- Check current cached TTL before planning:
dig +nocmd +noall +answer example.com - After migration stable 24h, raise TTL back to 3600-86400s
- Test with multiple resolvers: Google (8.8.8.8), Cloudflare (1.1.1.1), local ISP—they cache independently
Email Authentication (All Three Required)
- SPF alone insufficient—DKIM and DMARC both needed for deliverability
- DMARC record:
_dmarc.example.com TXT "v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com" - SPF must be single TXT record—multiple SPF records invalid; use
include: for multiple sources - SPF ending:
-all (reject) or ~all (soft fail)—never +all or ?all - Verify complete setup with mail-tester.com after configuration
CAA Records
- Limits which Certificate Authorities can issue certs for domain—prevents unauthorized issuance
- Basic:
example.com. CAA 0 issue "letsencrypt.org" - Wildcard requires separate entry:
CAA 0 issuewild "letsencrypt.org" - Incident reporting:
CAA 0 iodef "mailto:security@example.com" - Without CAA, any CA can issue—set explicitly for security-conscious domains
www Handling
- Configure both apex and www—or redirect one to other; leaving www unconfigured breaks links
- Pick canonical form and stick to it: www → apex OR apex → www
- HTTPS redirect requires cert for both variants before redirect works
- Test both URLs explicitly after setup
Debugging Commands
dig +trace example.com—full resolution chain from root; reveals where problem occursdig @ns1.provider.com example.com—query authoritative nameserver directly, bypasses cache- Compare authoritative vs cached response—mismatch indicates propagation in progress
- Check all relevant record types—A working doesn't mean AAAA, MX, or TXT are correct
Cloudflare Proxy Behavior
- Orange cloud (proxied) hides origin IP—breaks SSH, mail, game servers; use grey cloud for non-HTTP
- Proxied records ignore your TTL setting—Cloudflare controls caching
- CNAME flattening at apex works in Cloudflare but causes confusion when migrating away
- Universal SSL only on proxied records—DNS-only requires origin certificate
Wildcard Records
*.example.com does not match apex example.com—both need explicit records- Explicit subdomain record takes precedence over wildcard
- Wildcard SSL certificates require separate issuance—use DNS challenge with Let's Encrypt
版本历史
共 1 个版本
-
v1.0.0
当前
2026-03-29 02:02 安全 安全
安全检测
腾讯云安全 (Sanbu)
安全,无风险
查看报告
🔗 相关推荐
ai-intelligence
ivangdavila
自我反思+自我批评+自我学习+自组织记忆。智能体评估自身工作、发现错误并持续改进。
★ 1,349
📥 317,700
security-compliance
thomaslwang
MoltGuard — OpenClaw 安全守卫,由 OpenGuardrails 提供。安装 MoltGuard,保护您和您的用户免受提示注入、数据泄露和恶意攻击。
★ 116
📥 30,699
security-compliance
spclaudehome
AI智能体技能安全预审工具。安装ClawdHub、GitHub等来源技能前,检查风险信号、权限范围及可疑模式。
★ 1,210
📥 266,156