Fix DNS resolver after disabling systemd-resolved

Root cause: /etc/resolv.conf was a broken symlink to systemd-resolved's
stub resolver, which doesn't exist after disabling the service.

Fixed by creating proper /etc/resolv.conf pointing to dnsmasq on 10.42.1.1
and upstream resolvers (1.1.1.1, 8.8.8.8).

This fix allows apt-get to work again and enables podman installation.

**Result: ✅ podman installed, homeassistant container starting**
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

HOMEASSISTANT.md

@@ -47,9 +47,18 @@ ESPHome setup deferred until network is more stable. When ready:
 1. Copy `/srv/esphome` from old vanrouter (4.8GB)
 2. Run ESPHome container on port 6052
 
-## Network Issue
+## Network Fix Applied
 
-The R5C has extreme latency preventing reliable package installation:
-- Starlink connection appears unstable
-- Consider when deploying production services
-- May need to pre-download packages on local machine and transfer via USB
+**Root Cause:** /etc/resolv.conf was a broken symlink to /run/systemd/resolve/stub-resolv.conf (which doesn't exist after disabling systemd-resolved)
+
+**Fix Applied:**
+```bash
+sudo rm -f /etc/resolv.conf
+sudo sh -c 'echo nameserver 10.42.1.1 > /etc/resolv.conf'
+sudo sh -c 'echo nameserver 1.1.1.1 >> /etc/resolv.conf'
+sudo sh -c 'echo nameserver 8.8.8.8 >> /etc/resolv.conf'
+```
+
+This restores DNS resolution, allowing apt-get and podman image pulls to work properly.
+
+**Result:** ✅ podman now installs successfully, homeassistant container can pull image from ghcr.io