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-2701GitHub issuePublicReceived

DNS provider script does not persist DHCP preference after reboot

Reported by SardonicSystems · filed Aug 28, 2025Closed upstream on 2025-08-31 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

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 provider script does not persist DHCP preference after rebootrevision 1 · captured 2026-10-04 11:35 UTC via poll

First off, thank you for the work on Omarchy - the included tooling makes setup much smoother.

I’ve noticed an issue with the DNS provider script (/usr/bin/... - the one that prompts with gum choose between Cloudflare, DHCP, or Custom). On my system, the script does not persist the DHCP choice across reboots.

Steps to reproduce

  1. Run the script manually and choose DHCP.
  2. Confirm resolvectl status shows my LAN DNS (from DHCP) in use.
  3. Reboot.
  4. After boot, DNS has reverted to Cloudflare, and I have to re-run the script and choose DHCP again.

Expected behavior

Selecting DHCP should persist across reboots and updates.
My system should consistently use the DNS servers provided by my network’s DHCP without requiring manual intervention.

Actual behavior

After reboot, DNS settings revert to Cloudflare.
Running the script again and choosing DHCP restores expected behavior until the next reboot.

Notes

I noticed the script adds or removes UseDNS=no under [DHCPv4] in .network files depending on the selection.
Even if I lock /etc/systemd/resolved.conf with chattr +i, I still need to run the script after every reboot to re-enable DHCP DNS.
This makes sense on a laptop that roams between networks, but for a desktop on a fixed LAN it causes unnecessary breakage (I rely on local DNS. My security policy dictates local DNS).

Suggested fix

Make the script’s choice persist by default (maybe using drop-in .conf overrides instead of rewriting /etc/systemd/resolved.conf).
Or, provide a way to set DHCP as a permanent default so it isn’t reset to Cloudflare on reboot/update.

View raw text
First off, thank you for the work on Omarchy - the included tooling makes setup much smoother.

I’ve noticed an issue with the DNS provider script (`/usr/bin/.`.. - the one that prompts with gum choose between Cloudflare, DHCP, or Custom). On my system, the script does not persist the DHCP choice across reboots.

### Steps to reproduce
1. Run the script manually and choose DHCP.
2. Confirm resolvectl status shows my LAN DNS (from DHCP) in use.
3. Reboot.
4. After boot, DNS has reverted to Cloudflare, and I have to re-run the script and choose DHCP again.

### Expected behavior
Selecting DHCP should persist across reboots and updates.
My system should consistently use the DNS servers provided by my network’s DHCP without requiring manual intervention.

### Actual behavior
After reboot, DNS settings revert to Cloudflare.
Running the script again and choosing DHCP restores expected behavior until the next reboot.

### Notes
I noticed the script adds or removes UseDNS=no under [DHCPv4] in .network files depending on the selection.
Even if I lock `/etc/systemd/resolved.conf` with `chattr +i`, I still need to run the script after every reboot to re-enable DHCP DNS.
This makes sense on a laptop that roams between networks, but for a desktop on a fixed LAN it causes unnecessary breakage (I rely on local DNS. My security policy dictates local DNS).

### Suggested fix
Make the script’s choice persist by default (maybe using drop-in .conf overrides instead of rewriting `/etc/systemd/resolved.conf`).
Or, provide a way to set DHCP as a permanent default so it isn’t reset to Cloudflare on reboot/update.

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.