jsutter/nixos
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update DNS procedure to use non-proxied Cloudflare records

Browse source
This commit is contained in:
Julian Sutter 2026-02-16 22:18:36 -08:00
parent 7db4dc3f25
commit 46b60f6ade
1 changed files with 2 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

3
agents.md
View file

@ -98,10 +98,11 @@ curl -m 5
curl -s -X POST "https://api.cloudflare.com/client/v4/zones/$ZONE_ID/dns_records" \ curl -s -X POST "https://api.cloudflare.com/client/v4/zones/$ZONE_ID/dns_records" \
-H "Authorization: Bearer <CLOUDFLARE_API_TOKEN>" \ -H "Authorization: Bearer <CLOUDFLARE_API_TOKEN>" \
-H "Content-Type: application/json" \ -H "Content-Type: application/json" \
--data '{"type":"A","name":"<subdomain>","content":"<IP_ADDRESS>","ttl":1,"proxied":true}' --data '{"type":"A","name":"<subdomain>","content":"<IP_ADDRESS>","ttl":1,"proxied":false}'
``` ```
**Common DNS Issues:** **Common DNS Issues:**
- Local DNS caching: Add entry to `/etc/hosts` temporarily for testing - Local DNS caching: Add entry to `/etc/hosts` temporarily for testing
- Cloudflare proxy can cause SSL/TLS handshake failures - use non-proxied (grey cloud) records for direct server access
- Use Cloudflare's proxy IPs directly if DNS propagation is slow - Use Cloudflare's proxy IPs directly if DNS propagation is slow
8. **Process Improvement** 8. **Process Improvement**