docs(dns): replace local absolute paths with GitHub-safe relative links
This commit is contained in:
Brian Pooe
parent
54fe6dda98
commit
795da7bffb
6 changed files with 21 additions and 21 deletions
|
|
@ -8,7 +8,7 @@ Use this as the single flow document. Each step links to the deeper guide where
|
|||
- Pi-hole teleporter tarball
|
||||
2. Keep the old Pi Zero 2 W untouched until final cutover is stable.
|
||||
3. Review your analyzed current-state map:
|
||||
- [Current architecture analysis](/Users/luda/Documents/synology-docker-services/dns/pfsense-pihole-technitium-analysis.md)
|
||||
- [pfsense-pihole-technitium-analysis.md](./pfsense-pihole-technitium-analysis.md)
|
||||
|
||||
## 2) Prepare the new Pi 4 with a temporary DNS IP
|
||||
1. Connect Pi 4 to the same Adblock VLAN (`192.168.60.0/24`).
|
||||
|
|
@ -52,8 +52,8 @@ docker compose -f docker-compose-files/technitium-dockhand.yaml up -d
|
|||
```
|
||||
|
||||
Reference:
|
||||
- [Technitium + Dockhand deployment guide](/Users/luda/Documents/synology-docker-services/dns/technitium-dockhand-deployment.md)
|
||||
- [Compose template](/Users/luda/Documents/synology-docker-services/docker-compose-files/technitium-dockhand_template.yaml)
|
||||
- [technitium-dockhand-deployment.md](./technitium-dockhand-deployment.md)
|
||||
- [technitium-dockhand_template.yaml](../docker-compose-files/technitium-dockhand_template.yaml)
|
||||
|
||||
## 4) Configure Technitium to mirror current behavior
|
||||
1. Open Technitium UI on Pi 4 temporary IP:
|
||||
|
|
@ -72,7 +72,7 @@ Reference:
|
|||
- `www.googleadservices.com`
|
||||
|
||||
Reference:
|
||||
- [Technitium cutover checklist](/Users/luda/Documents/synology-docker-services/dns/technitium-cutover-checklist.md)
|
||||
- [technitium-cutover-checklist.md](./technitium-cutover-checklist.md)
|
||||
|
||||
## 5) Pre-cutover validation on temporary IP
|
||||
From clients (or directly from Pi 4), validate against `192.168.60.6`:
|
||||
|
|
@ -88,13 +88,13 @@ If these fail, do not proceed to IP swap.
|
|||
If not already done, apply forced DNS interception for LAN + VLANs.
|
||||
|
||||
Reference (fast entry):
|
||||
- [Forced DNS quick entry](/Users/luda/Documents/synology-docker-services/dns/pfsense-forced-dns-quick-entry.md)
|
||||
- [pfsense-forced-dns-quick-entry.md](./pfsense-forced-dns-quick-entry.md)
|
||||
|
||||
Reference (full explanation):
|
||||
- [Forced DNS all VLANs](/Users/luda/Documents/synology-docker-services/dns/pfsense-forced-dns-all-vlans.md)
|
||||
- [pfsense-forced-dns-all-vlans.md](./pfsense-forced-dns-all-vlans.md)
|
||||
|
||||
Optional hardening for encrypted DNS bypass:
|
||||
- [DoT/DoH blocking quick entry](/Users/luda/Documents/synology-docker-services/dns/pfsense-dot-doh-blocking-quick-entry.md)
|
||||
- [pfsense-dot-doh-blocking-quick-entry.md](./pfsense-dot-doh-blocking-quick-entry.md)
|
||||
|
||||
## 7) Safe same-IP handover (make Pi 4 become `192.168.60.5`)
|
||||
1. Schedule a short maintenance window.
|
||||
|
|
|
|||
|
|
@ -109,7 +109,7 @@ flowchart LR
|
|||
|
||||
## Fast entry version
|
||||
If you want one block per interface for direct UI entry, use:
|
||||
- `/Users/luda/Documents/synology-docker-services/dns/pfsense-forced-dns-quick-entry.md`
|
||||
- [pfsense-forced-dns-quick-entry.md](./pfsense-forced-dns-quick-entry.md)
|
||||
|
||||
Related hardening quick-entry:
|
||||
- `/Users/luda/Documents/synology-docker-services/dns/pfsense-dot-doh-blocking-quick-entry.md`
|
||||
- [pfsense-dot-doh-blocking-quick-entry.md](./pfsense-dot-doh-blocking-quick-entry.md)
|
||||
|
|
|
|||
|
|
@ -138,4 +138,4 @@ Minimum extra control:
|
|||
- Add block rules for outbound TCP/UDP `853` on LAN/OPT2/OPT3/OPT4/OPT5/OPT6.
|
||||
|
||||
Related hardening quick-entry:
|
||||
- `/Users/luda/Documents/synology-docker-services/dns/pfsense-dot-doh-blocking-quick-entry.md`
|
||||
- [pfsense-dot-doh-blocking-quick-entry.md](./pfsense-dot-doh-blocking-quick-entry.md)
|
||||
|
|
|
|||
|
|
@ -180,4 +180,4 @@ flowchart LR
|
|||
|
||||
## Companion runbook
|
||||
For step-by-step cutover execution and wildcard-vs-explicit record strategy, see:
|
||||
- `/Users/luda/Documents/synology-docker-services/dns/technitium-cutover-checklist.md`
|
||||
- [technitium-cutover-checklist.md](./technitium-cutover-checklist.md)
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# Technitium Cutover Checklist (From Current pfSense + Pi-hole)
|
||||
|
||||
Start-here master flow:
|
||||
- `/Users/luda/Documents/synology-docker-services/dns/end-to-end-migration-runbook.md`
|
||||
- [end-to-end-migration-runbook.md](./end-to-end-migration-runbook.md)
|
||||
|
||||
## Short answer: do you need 26 CNAME records?
|
||||
No, not if all your app hostnames should resolve to Caddy.
|
||||
|
|
@ -44,8 +44,8 @@ A wildcard record closes this drift gap permanently.
|
|||
## Cutover plan
|
||||
|
||||
### Docker stack files in this repo
|
||||
- Compose template: `/Users/luda/Documents/synology-docker-services/docker-compose-files/technitium-dockhand_template.yaml`
|
||||
- Deployment guide: `/Users/luda/Documents/synology-docker-services/dns/technitium-dockhand-deployment.md`
|
||||
- Compose template: [technitium-dockhand_template.yaml](../docker-compose-files/technitium-dockhand_template.yaml)
|
||||
- Deployment guide: [technitium-dockhand-deployment.md](./technitium-dockhand-deployment.md)
|
||||
|
||||
### 1. Keep network references stable
|
||||
- Keep Technitium service IP as `192.168.60.5`.
|
||||
|
|
@ -158,6 +158,6 @@ flowchart LR
|
|||
|
||||
## Related pfSense enforcement runbook
|
||||
For exact NAT/firewall settings to force DNS across LAN + VLANs, see:
|
||||
- `/Users/luda/Documents/synology-docker-services/dns/pfsense-forced-dns-all-vlans.md`
|
||||
- `/Users/luda/Documents/synology-docker-services/dns/pfsense-forced-dns-quick-entry.md`
|
||||
- `/Users/luda/Documents/synology-docker-services/dns/pfsense-dot-doh-blocking-quick-entry.md`
|
||||
- [pfsense-forced-dns-all-vlans.md](./pfsense-forced-dns-all-vlans.md)
|
||||
- [pfsense-forced-dns-quick-entry.md](./pfsense-forced-dns-quick-entry.md)
|
||||
- [pfsense-dot-doh-blocking-quick-entry.md](./pfsense-dot-doh-blocking-quick-entry.md)
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# Technitium + Dockhand Docker Deployment Guide
|
||||
|
||||
This guide deploys Technitium DNS and Dockhand using:
|
||||
- `/Users/luda/Documents/synology-docker-services/docker-compose-files/technitium-dockhand_template.yaml`
|
||||
- [technitium-dockhand_template.yaml](../docker-compose-files/technitium-dockhand_template.yaml)
|
||||
|
||||
Compatibility note:
|
||||
- Dockhand image in this stack is `fnsys/dockhand:latest` and should be run on 64-bit Linux (`arm64` on Pi 4).
|
||||
|
|
@ -64,16 +64,16 @@ Then configure:
|
|||
4. Add allowlist equivalent for `www.googleadservices.com`.
|
||||
|
||||
Reference details:
|
||||
- `/Users/luda/Documents/synology-docker-services/dns/technitium-cutover-checklist.md`
|
||||
- [technitium-cutover-checklist.md](./technitium-cutover-checklist.md)
|
||||
|
||||
## 5) pfSense integration
|
||||
Keep DNS server IP as `192.168.60.5` to avoid changing existing DHCP and firewall dependencies.
|
||||
|
||||
For forced DNS across all VLANs:
|
||||
- `/Users/luda/Documents/synology-docker-services/dns/pfsense-forced-dns-quick-entry.md`
|
||||
- [pfsense-forced-dns-quick-entry.md](./pfsense-forced-dns-quick-entry.md)
|
||||
|
||||
For DoT/DoH hardening:
|
||||
- `/Users/luda/Documents/synology-docker-services/dns/pfsense-dot-doh-blocking-quick-entry.md`
|
||||
- [pfsense-dot-doh-blocking-quick-entry.md](./pfsense-dot-doh-blocking-quick-entry.md)
|
||||
|
||||
## 6) Validation
|
||||
Run from clients on each VLAN:
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue