You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,6 +41,10 @@ Pi-DNStack is an automated solution for deploying a containerized DNS management
41
41
- Other distributions if dependencies are pre-installed
42
42
- Windows users can use [WSL2](https://docs.microsoft.com/en-us/windows/wsl/install)
43
43
44
+
> ⚠️ All deployment steps below should be run from your **workstation**, not directly on the target server.
45
+
> The script connects to the servers via SSH.
46
+
> You *can* use the server as its own workstation if it has PowerShell 7 and SSH access to itself, but that's not the main use case.
47
+
44
48
## Quick Start
45
49
46
50
1.**Clone Repository**
@@ -101,7 +105,7 @@ Pi-DNStack can automatically configure a Windows DHCP server to use Pi-hole. Thi
101
105
1. **Docker Network Mode**:
102
106
103
107
- If using `bridge` mode, ensure Pi-hole's DNS port is published (`piholeDnsPort = "53"`)
104
-
- If using `host` mode (recomenden when using this feature), ensure the host's firewall allows DNS traffic and unbound is disabled (both containers would use port 53)
108
+
- If using `host` mode (recommended when using this feature), ensure the host's firewall allows DNS traffic and unbound is disabled (both containers would use port 53)
105
109
106
110
2. **Pi-hole Listen Configuration**:
107
111
- Ensure Pi-hole is configured to listen to the required interfaces.
0 commit comments