Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-2501GitHub issuePublicReceived

DNS Configuration Issue

Reported by jardahrazdera · filed Aug 13, 2025Closed upstream on 2025-08-24 by the merge of PR #752 (closed by dhh). GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
Not yet mapped to any requirement or component.
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

DNS Configuration Issuerevision 1 · captured 2026-10-04 11:27 UTC via poll

DNS Configuration Issue

This approach has significant limitations for local development environments. When you have a server on LAN with a local IP address and your router serves DNS, the dotfiles break this setup completely.

Why should I modify /etc/hosts etc. when I already have everything configured properly? These dotfiles force public DNS, which makes no sense for a developer-focused tool. Local DNS resolution is essential for development environments with local servers.

The current approach lacks logic - it assumes everyone wants public DNS and breaks existing, working network configurations.

My setup:

  • Router DNS: 192.\.\.1 (handles local names)
  • Local server: example.com → 192.\.\.* (LAN IP)
  • Current DNS resolution: working perfectly via router

After applying Omarchy update 1.13.0:

  • Forced DNS: 1.1.1.1/8.8.8.8 (public only)
  • Local server: example.com → public IP (breaks local access)
  • Result: can't reach local services by domain name

Solutions:

Best approach: Let DHCP do its job.

Alternative fix: You can restore local DNS resolution with this command (replace <your_gateway_ip> with your router's IP):

sudo sed -i 's/^DNS=.*/DNS=<your_gateway_ip>/' /etc/systemd/resolved.conf && \
sudo sed -i 's/^FallbackDNS=.*/FallbackDNS=1.1.1.1/' /etc/systemd/resolved.conf

Or just use DHCP

sudo sed -i '/^DNS=/d' /etc/systemd/resolved.conf
sudo sed -i '/^FallbackDNS=/d' /etc/systemd/resolved.conf

And don't forget to restart resolved

sudo systemctl restart systemd-resolved
View raw text
# DNS Configuration Issue

This approach has significant limitations for local development environments. When you have a server on LAN with a local IP address and your router serves DNS, the dotfiles break this setup completely.

Why should I modify `/etc/hosts` etc. when I already have everything configured properly? These dotfiles force public DNS, which makes no sense for a developer-focused tool. Local DNS resolution is essential for development environments with local servers.

The current approach lacks logic - it assumes everyone wants public DNS and breaks existing, working network configurations.

## My setup:
- Router DNS: 192.\*.\*.1 (handles local names)
- Local server: example.com → 192.\*.\*.* (LAN IP)
- Current DNS resolution: working perfectly via router

## After applying Omarchy update 1.13.0:
- Forced DNS: 1.1.1.1/8.8.8.8 (public only)
- Local server: example.com → public IP (breaks local access)
- Result: can't reach local services by domain name

## Solutions:

**Best approach:** Let DHCP do its job.

**Alternative fix:** You can restore local DNS resolution with this command (replace `<your_gateway_ip>` with your router's IP):

```bash
sudo sed -i 's/^DNS=.*/DNS=<your_gateway_ip>/' /etc/systemd/resolved.conf && \
sudo sed -i 's/^FallbackDNS=.*/FallbackDNS=1.1.1.1/' /etc/systemd/resolved.conf
```
Or just use DHCP

```bash
sudo sed -i '/^DNS=/d' /etc/systemd/resolved.conf
sudo sed -i '/^FallbackDNS=/d' /etc/systemd/resolved.conf
```
And don't forget to restart `resolved`

```bash
sudo systemctl restart systemd-resolved
```

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

No decision has been recorded yet.