mirror of
https://github.com/mageddo/dns-proxy-server.git
synced 2026-04-25 17:35:54 +03:00
[GH-ISSUE #62] DPS Lose DNS server configuration after system unsuspension, or network configuration #26
Labels
No labels
bug
confirmed
discussion
duplicate
enhancement
feature
feature-request
not-planned
pull-request
secondary-feature
stale
triage
waiting-feedback
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/dns-proxy-server-mageddo#26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mageddo on GitHub (Mar 1, 2018).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/62
Using
-default-dnsDPS will be settled as default Linux DNS. If you suspend linux DPS will not be the default DNS server after unsuspend. It also happen sometimes if you unplug and plug network cable or wifi.@fezfez commented on GitHub (May 17, 2018):
@mageddo : same for me, i have to stop and start the service when i lost wifi connection
@mageddo commented on GitHub (May 17, 2018):
I think DPS will have to monitor host machine DNS configurations while it is running
@mageddo commented on GitHub (May 31, 2018):
@fezfez Fixed at
2.5.4DPS will monitor resolvconf and update that every 20 seconds if necessary@fezfez commented on GitHub (May 31, 2018):
@mageddo : thanks for your awesome work !