WireGuard was connected, Technitium was alive, and .fndhome records existed. The problem was that wg-easy generated client profiles using the wg-easy host as DNS instead of Technitium.
June
The VPN tunnel connected. The phone showed WireGuard as active. Technitium DNS was running. Internal records existed. From the server side, everything looked like it should work.
But the phone still was not resolving internal .fndhome names correctly. The actual problem was the DNS value in the WireGuard client profile. wg-easy was handing out the wg-easy host as DNS instead of the Technitium DNS server.
The fix was to change wg’s DNS setting to Technitium, regenerate or update the client profile, reload it on the phone, and verify Technitium live logs actually saw the phone’s queries.
VPN connected does not mean DNS is right.
It's not DNS
There's no way it's DNS
It was DNS
-- a DNS haikumands hereThe family portal looked dead, replacement CMS options started getting judged, and then the whole “incident” turned out to be a forgotten login.
early March
The Family Portal was running on Ghost and appeared broken. Instead of starting with boring triage, the problem immediately felt bigger than it was. WordPress got dragged back into the conversation. Concrete CMS got judged. The whole platform was briefly on trial.
Then the boring answer showed up. Ghost was not destroyed. The container was fine. The login credentials were the problem.
Once the password was reset inside the container, the “outage” was basically over
Before replacing the whole platform, make sure the platform is actually broken.
paste commands here