Skip to content

Never stop an app that answers DNS for its backup - #7

Merged
inkly merged 1 commit into
mainfrom
fix/dns-app-hold-still
Sep 24, 2026
Merged

inkly merged 1 commit into
mainfrom
fix/dns-app-hold-still

Conversation

@inkly

@inkly inkly commented Sep 24, 2026

Copy link
Copy Markdown
Collaborator

Backing up AdGuard Home or Pi-hole with hold still stopped the DNS server for the copy: the box lost its lookups and a cloud copy failed on DNS (ReCasaOS/CasaOS#7), and the whole network lost its names meanwhile. An app publishing port 53, or AdGuard Home/Pi-hole on the host network, is now copied running; the History records whether the app was really stopped.

A backup held still stops the app it copies. When that app is the DNS
server (AdGuard Home, Pi-hole), the box loses its own lookups for the
length of the copy when it uses that server, so a copy to a cloud
destination fails at its first one (ReCasaOS/CasaOS#7), and the whole
network loses its names meanwhile. An app that publishes port 53, or
AdGuard Home or Pi-hole on the host's network, is now copied running.
The History records whether the app was really stopped, not whether it
was asked to be.
@inkly
inkly merged commit d2825b0 into main Sep 24, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant