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.

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

Query DNS upon archive get #130

Open
Divide-By-0 opened this issue Dec 4, 2024 · 2 comments · May be fixed by #139
Open

Query DNS upon archive get #130

Divide-By-0 opened this issue Dec 4, 2024 · 2 comments · May be fixed by #139
Labels
easy enhancement New feature or request high

Comments

@Divide-By-0
Copy link
Member

Upon receiving any query, quickly double check DNS to see if we should forward-date the local value's timestamp

@Divide-By-0 Divide-By-0 added enhancement New feature or request high easy labels Dec 4, 2024
@Pratham1812
Copy link

Hey @Divide-By-0 can I get a little more clarity on this issue?

@Divide-By-0
Copy link
Member Author

Basically call /dsp when /key is called and refer to that result if needed, with a flag to disable that call to make the response faster.

devin-ai-integration bot added a commit that referenced this issue Dec 24, 2024
- Add DNS refresh logic before fetching records
- Use existing refreshKeysFromDns function to update timestamps
- Maintain rate limiting and error handling

Co-Authored-By: Yush G <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
easy enhancement New feature or request high
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants