Update incident: DHCP DNS fix for device connectivity

2026-01-25 13:27:26 +02:00
parent 776372a0b9
commit b0f78c5022
2 changed files with 88 additions and 0 deletions
@@ -86,3 +86,42 @@ After fix:
 ---

 *Incident logged by Claude Code via Tailscale connection*
+
+---
+
+## Additional Issue: Devices No Internet (13:25)
+
+### Symptom
+- LG TV and other devices showing no internet connection
+- DNS changes not reaching devices
+
+### Root Cause
+DHCP was pushing  as DNS to clients, but MikroTik NAT rules redirect all port 53 traffic to AdGuard. This created a mismatch.
+
+**Before:**
+```
+DHCP DNS-SERVER: 8.8.8.8
+```
+
+### Fix
+Changed DHCP to push MikroTik as DNS (which forwards to AdGuard):
+
+```bash
+/ip dhcp-server network set 0 dns-server=192.168.31.1
+```
+
+**After:**
+```
+DHCP DNS-SERVER: 192.168.31.1
+```
+
+### DNS Flow (Corrected)
+```
+Device → 192.168.31.1 (MikroTik DNS) → 192.168.31.4 (AdGuard) → 8.8.8.8 (upstream)
+```
+
+### Device Recovery
+Devices need to renew DHCP lease to get new DNS:
+- Wait for lease expiry (default 10 min)
+- Reconnect to WiFi
+- Reboot device