Update DNS procedure to use non-proxied Cloudflare records
This commit is contained in:
parent
7db4dc3f25
commit
46b60f6ade
1 changed files with 2 additions and 1 deletions
|
|
@ -98,10 +98,11 @@ curl -m 5
|
|||
curl -s -X POST "https://api.cloudflare.com/client/v4/zones/$ZONE_ID/dns_records" \
|
||||
-H "Authorization: Bearer <CLOUDFLARE_API_TOKEN>" \
|
||||
-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:**
|
||||
- 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
|
||||
|
||||
8. **Process Improvement**
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue