Implement DNS cache warning during installation #321
Labels
No Label
Blocked
Bug
Contributions welcome
Did not do
Errata
Feature request
Fixed
How To
Invalid
Needs design
No resolution
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Providers
Digital Ocean
Providers
Hetzner
Refactor
Severity
High
Severity
Low
Severity
Medium
Source
Community
Source
Core Team
Source
Stakeholders
Translations
Under investigation
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Blocks
#84 DNSSEC failures are not handled
SelfPrivacy/selfprivacy.org.app
Reference: SelfPrivacy/selfprivacy.org.app#321
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
During installation DNS cache can prevent successful API deployment.
Steps to reproduce
Expected behavior
Most likely during "1 out 4" stage DNS will re-use previous IP due to records TTL, and the application shows the mismatch on UI.
Actual behavior
During "1 out 4" stage the previous IP gets reused and all DNS checks clog without any explanation or assistance for user.
Note
Related: 84.