Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

flush dns cache with resolved. #2144

Open
majestrate opened this issue Mar 6, 2023 · 0 comments
Open

flush dns cache with resolved. #2144

majestrate opened this issue Mar 6, 2023 · 0 comments
Assignees
@jagerman
Labels
dns issues related to DNS (because "it's always DNS") linux linux specific issue packaging
Milestone
0.10.x

Comments

@majestrate
Copy link
Contributor

majestrate commented Mar 6, 2023 •
edited
Loading

we should call resolvectl flush-caches after lokinet.service goes up (or maybe down) to get rid of cached negative replies that systemd-resolved may have got from lokinet.
@majestrate majestrate added packaging dns issues related to DNS (because "it's always DNS") linux linux specific issue labels Mar 6, 2023
@majestrate majestrate added this to the 0.9.12 milestone Mar 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jagerman jagerman

Labels
dns issues related to DNS (because "it's always DNS") linux linux specific issue packaging
Projects
None yet
Milestone
0.10.x
Development

No branches or pull requests
2 participants
@majestrate @jagerman