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

[Feature Request] Allow specific domains/records to bypass cache #928

Open
NebulaMods opened this issue May 20, 2024 · 3 comments
Open

[Feature Request] Allow specific domains/records to bypass cache #928

NebulaMods opened this issue May 20, 2024 · 3 comments

Comments

@NebulaMods
Copy link

It would be cool if Technitium could disable caching for a specific domain, record, or even zone.

This came to my mind for doing ACME DNS challenges for wildcard certificates, cache can cause some issues on the TXT records. So having the ability to whitelist said record, would make things simpler, and Adguard Home also has this ability if I am not mistaken.

@Hemsby
Copy link

Hemsby commented May 20, 2024

I set the TTL for this to 0 for this reason. Only for this records. Stops clients and others caching it.

@ShreyasZare
Copy link
Member

Thanks for the request. Adding such an option will actually be too complex to add and configure. Instead, I would suggest that you use the HTTP API to delete cache for specific domain name in your cert renewal process/script. You will need to generate a auth token from the admin panel to use with that HTTP GET call.

@NebulaMods
Copy link
Author

I set the TTL for this to 0 for this reason. Only for this records. Stops clients and others caching it.

Ah, this is smart. I didn't think of that.

Thanks for the request. Adding such an option will actually be too complex to add and configure. Instead, I would suggest that you use the HTTP API to delete cache for specific domain name in your cert renewal process/script. You will need to generate a auth token from the admin panel to use with that HTTP GET call.

Oh okay, thanks for the tip.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants