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

[Support Request] DNS Cache problem #83

Closed
BOBINIUNIU opened this issue May 13, 2023 · 8 comments · Fixed by #87
Closed

[Support Request] DNS Cache problem #83

BOBINIUNIU opened this issue May 13, 2023 · 8 comments · Fixed by #87
Assignees
@mzz2017

Comments

@BOBINIUNIU
Copy link

What happened:

Does dae have DNS cache? I have DDNS configured on my router and nslookup can return the correct IP if not connected through dae. If connected via dae it always returns the old IP unless I restart the dae service

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know

Environment:

  • Dae version (use dae --version):
  • OS (e.g cat /etc/os-release):
  • Kernel (e.g. uname -a):
  • Others:
@mzz2017
Copy link
Contributor

mzz2017 commented May 13, 2023

@BOBINIUNIU Yes. dae has cache. You expect to bypass cache for some domains?

@piyoki piyoki changed the title DNS Cache problem [Support Request] DNS Cache problem May 13, 2023
@BOBINIUNIU
Copy link
Author

@BOBINIUNIU Yes. dae has cache. You expect to bypass cache for some domains?
No, we don't need new feature. The problem is the cached results cannot be updated.
The TTL for my domain is 10 minutes, however, the nslookup command query is still returning cached results after few hours. dae should update the cached result after the TTL expires.

@BOBINIUNIU
Copy link
Author

Could you please add a switch to disable dae dns cache? Users who use external dns services may encounter some problems.

@mzz2017
Copy link
Contributor

mzz2017 commented May 14, 2023

@BOBINIUNIU DNS cache should update after ttl. I'll check it.

@BOBINIUNIU
Copy link
Author

I think a dns cache switch is the best solution. This would avoid the problems caused by multiple dns caches.

@MarksonHon
Copy link
Contributor

你可以说中文的
Actually you can speak Chinese here

@piyoki
Copy link
Contributor

piyoki commented May 14, 2023

@MarksonHon 🌚🌚🌚

@BOBINIUNIU
Copy link
Author

BOBINIUNIU commented May 14, 2023 •
edited
Loading

你可以说中文的 Actually you can speak Chinese here

Actually we all can speak Chinese here, only the people in the WALL use this software. 蛤蛤

@mzz2017 mzz2017 mentioned this issue May 14, 2023
Merged
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mzz2017 mzz2017

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(dns): cache would never expire caused by #63 by accident daeuniverse/dae
4 participants
@BOBINIUNIU @mzz2017 @piyoki @MarksonHon