feat(dashy): switch service URLs to .lan hostnames #20

Open
renovate-bot wants to merge 1 commit from feature/dashy-lan-hostnames into main
Collaborator

Summary

  • Replaces all hardcoded IP addresses in dashy/conf.yml with .lan hostnames
  • Hostnames are resolved by Adguard Home DNS rewrites
  • Makes the dashboard resilient to IP changes � update Adguard, not the dashboard
  • Fios router kept as IP (192.168.1.1) � no hostname needed

DO NOT MERGE until DNS is working on all your devices

This PR will break Dashy links on any device that is not using Adguard (192.168.1.86) as its DNS server. Currently .lan hostnames only resolve on Atlas (DNS set manually). Your phone, tablet, and other network devices will get ERR_NAME_NOT_RESOLVED for every link in Dashy.

How to fix DNS on your other devices

The real fix — make the Fios router push Adguard as the DNS server to all DHCP clients:

  1. Go to https://192.168.1.1 → log in to the Fios router
  2. Navigate to My NetworkNetwork Connections
  3. Click on Broadband Connection (Ethernet/Coax) or your WAN connection → Settings
  4. Look for DNS Server or LAN DNS settings
  5. If there is an option to set the DHCP DNS server (the DNS pushed to clients), set it to 192.168.1.86
  6. Save and reboot the router
  7. Reconnect your phone and other devices — they should now receive 192.168.1.86 as their DNS server automatically
  8. Verify on your phone: Settings → Wi-Fi → your network → DNS should show 192.168.1.86

Note: Fios routers often lock the DHCP DNS to their own IP and only expose upstream DNS forwarding settings. If the router does not have a DHCP DNS override option, the alternative is to set DNS manually on each device (Wi-Fi settings → static DNS → 192.168.1.86) or configure your DHCP server to advertise Adguard as the DNS server to all clients.

Once all devices resolve .lan hostnames, merge this PR.

## Summary - Replaces all hardcoded IP addresses in `dashy/conf.yml` with `.lan` hostnames - Hostnames are resolved by Adguard Home DNS rewrites - Makes the dashboard resilient to IP changes � update Adguard, not the dashboard - Fios router kept as IP (`192.168.1.1`) � no hostname needed ## ⛔ DO NOT MERGE until DNS is working on all your devices This PR will break Dashy links on any device that is **not** using Adguard (192.168.1.86) as its DNS server. Currently `.lan` hostnames only resolve on Atlas (DNS set manually). Your phone, tablet, and other network devices will get `ERR_NAME_NOT_RESOLVED` for every link in Dashy. ### How to fix DNS on your other devices **The real fix — make the Fios router push Adguard as the DNS server to all DHCP clients:** 1. Go to **https://192.168.1.1** → log in to the Fios router 2. Navigate to **My Network** → **Network Connections** 3. Click on **Broadband Connection (Ethernet/Coax)** or your WAN connection → **Settings** 4. Look for **DNS Server** or **LAN DNS** settings 5. If there is an option to set the **DHCP DNS server** (the DNS pushed to clients), set it to `192.168.1.86` 6. Save and reboot the router 7. Reconnect your phone and other devices — they should now receive `192.168.1.86` as their DNS server automatically 8. Verify on your phone: **Settings → Wi-Fi → your network → DNS** should show `192.168.1.86` > **Note:** Fios routers often lock the DHCP DNS to their own IP and only expose upstream DNS forwarding settings. If the router does not have a DHCP DNS override option, the alternative is to set DNS manually on each device (Wi-Fi settings → static DNS → `192.168.1.86`) or configure your DHCP server to advertise Adguard as the DNS server to all clients. **Once all devices resolve `.lan` hostnames, merge this PR.**
Replace hardcoded IP addresses in conf.yml with .lan hostnames
resolved by Adguard DNS. Makes dashboard resilient to IP changes.

Fios router (192.168.1.1) kept as IP — no .lan equivalent needed.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Author
Collaborator

BLOCKED � Do not merge yet.

This PR switches all Dashy URLs to .lan hostnames. On Atlas this works fine (DNS set manually to Adguard). But on your phone and any other device still using the Fios router for DNS, .lan will not resolve and every dashboard link will be broken.

Resolve the DNS issue on your other devices first, then merge. See the PR description for step-by-step instructions on how to make the Fios router push Adguard to all DHCP clients.

⛔ **BLOCKED � Do not merge yet.** This PR switches all Dashy URLs to `.lan` hostnames. On Atlas this works fine (DNS set manually to Adguard). But on your phone and any other device still using the Fios router for DNS, `.lan` will not resolve and every dashboard link will be broken. Resolve the DNS issue on your other devices first, then merge. See the PR description for step-by-step instructions on how to make the Fios router push Adguard to all DHCP clients.
matt force-pushed feature/dashy-lan-hostnames from 3f24aed109 to fd758c1025 2026-04-26 02:01:49 +00:00 Compare
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feature/dashy-lan-hostnames:feature/dashy-lan-hostnames
git switch feature/dashy-lan-hostnames

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff feature/dashy-lan-hostnames
git switch feature/dashy-lan-hostnames
git rebase main
git switch main
git merge --ff-only feature/dashy-lan-hostnames
git switch feature/dashy-lan-hostnames
git rebase main
git switch main
git merge --no-ff feature/dashy-lan-hostnames
git switch main
git merge --squash feature/dashy-lan-hostnames
git switch main
git merge --ff-only feature/dashy-lan-hostnames
git switch main
git merge feature/dashy-lan-hostnames
git push origin main
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
matt/homelab-docker!20
No description provided.