fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
3.2 KiB
3.2 KiB
UDM Pro — Cloudflare DNS Setup
Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation
Purpose: Configure UniFi Dream Machine Pro to use Cloudflare DNS (1.1.1.1, 1.0.0.1) for DHCP clients and for the gateway itself. This ensures consistent resolution across your network and can resolve mobile "URL not found" issues.
Why Cloudflare DNS
- Consistent resolution — Same results across desktop, mobile, and internal services
- Faster propagation — Cloudflare is authoritative for d-bis.org and related zones
- Bypasses carrier DNS — Mobile clients on Wi‑Fi use your LAN DHCP → Cloudflare
- Privacy — Cloudflare DNS doesn't sell query data
1. DHCP DNS for Clients (Recommended)
Clients that get DHCP from UDM Pro will use Cloudflare DNS.
Steps (UniFi Network Controller)
- Open UniFi Network (controller)
- Go to Settings (gear icon) → Networks
- Edit your primary LAN network (e.g. LAN, Default, or the network serving 192.168.11.x)
- Expand DHCP section
- Set DHCP Name Server to Manual
- Set:
- Name Server 1:
1.1.1.1 - Name Server 2:
1.0.0.1
- Name Server 1:
- Save → Controller will provision the UDM Pro
Result
- New DHCP leases and renewals will get 1.1.1.1 and 1.0.0.1 as DNS
- Existing clients get new DNS on next renewal (or reboot/reconnect)
2. UDM Pro Gateway DNS (Upstream)
The UDM Pro itself needs to resolve external hostnames (e.g. for UniFi services, NTP, updates). Set its upstream DNS to Cloudflare.
Steps (UniFi Network Controller)
- Settings → Networks → select your WAN network (or Internet)
- Or: Settings → Gateway → select the UDM Pro
- Find DNS Server or WAN DNS (varies by UniFi version)
- Set:
- Primary:
1.1.1.1 - Secondary:
1.0.0.1
- Primary:
- Save and apply
Alternative: System Settings
- Settings → System → Controller Settings
- Look for DNS or Network and set upstream DNS to 1.1.1.1, 1.0.0.1
3. Verify
From a client on your LAN
# Check which DNS you're using (after DHCP renewal)
# Windows: ipconfig /all
# Mac/Linux: cat /etc/resolv.conf or scutil --dns
# Test resolution
nslookup explorer.d-bis.org
# Should return 76.53.10.36
From UDM Pro (SSH, if enabled)
nslookup explorer.d-bis.org
4. Proxmox + Containers (Already Applied)
Proxmox hosts and LXC containers have been configured to use Cloudflare DNS directly:
- Proxmox hosts (r630-01, r630-02, ML110):
/etc/resolv.conf→ 1.1.1.1, 1.0.0.1 - LXC containers:
pct set <vmid> --nameserver "1.1.1.1 1.0.0.1"
To re-apply, run: scripts/apply-cloudflare-dns-proxmox.sh (if created).
5. Summary
| Component | DNS | Status |
|---|---|---|
| UDM Pro DHCP (clients) | 1.1.1.1, 1.0.0.1 | Manual in UniFi Controller |
| UDM Pro (gateway) | 1.1.1.1, 1.0.0.1 | Manual in UniFi Controller |
| Proxmox hosts | 1.1.1.1, 1.0.0.1 | ✅ Applied |
| LXC containers | 1.1.1.1, 1.0.0.1 | ✅ Applied |
| config/ip-addresses.conf | DNS_PRIMARY, DNS_SECONDARY | ✅ Updated |
Last updated: 2026-01-30