-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
[tteck, LXC] dns caching disabled #4699
Comments
You can activate nscd (Name service caching daemon) in the general settings. |
@CommanderStorm That's amazing, did not know something like that exists! |
Overlooked that you have installed a script by a third party. The reason is that your installation option does
We for now only enable this feature (and some others like "real browser") in containers to make the support effort somewhat manageable. uptime-kuma/server/uptime-kuma-server.js Lines 450 to 464 in 2957534
You can find the configuration file here: |
Okay I see, thanks for pointing that out, i'll let tteck know. |
I installed the service, injected your config and removed the part that checks for the variable in the shown code snippet, however at restart the js file was immediately rebuild, any hints on getting this to work? As the owner is not really that happy minded to implement it, I tought I can use the dns cache for http(s) domains, however after activating still each and every request went to my pihole instance. |
It is actually just downloaded to prevent OOM errors. See the third party script you use:
Either you:
|
Is docker variable and installing the service, starting and adding your config did not solve, but I switched to docker, makes |
@CommanderStorm Sorry to reopen this topic, but even after enabling the shown option oabove, and then after a while also enabling the other settings below the dns server setting also set to on i still get sooooo many dns requests, in 3 days I got like 75k just of uptime-kuma, is there any reason this cache is not working at all and the legacy cache also not? |
25k/day for 100 monitors Let me rephrase a previous comment (
=> Really difficult to gauge if this is excessive without additional data:
For the legacy caching please see #3762 Footnotes
|
I have not specifically configured nscp, is that neccessary? Okay yeah I also don't currently see it as a huge problem, it's just making reading dns logs and such things harded and it keeps my resolving quite high. I have got 37 monitors where roundabout 30 are different domains other ip/ping/dns TTL for my dns server is around 5-20ms depending on the domain. The thing is just currently there is no difference if dns cache is on or off, and in my eyes there should definitely be a notable difference. I just enabled legacy caching as well to see if it makes a difference. |
Use automated tooling such as anomaly detection or log based metrics via grafana loki and the likes.
Unclear what you mean
So basically TTL=0s => you have turned off DNS caching via this configuration |
It's not the thing that there are too many dns requests, but the fact that there is still the same amout than before enabling the cache, has to has to be some sort of issue.... Yes you are right I confused it with time. Not sure how I should be able to get the ttl. but I ran the following cmd found on the web from the uptime-kuma docker container which has my dns server as dns server.
|
So your TTL is 0 => caching is disabled |
Well then how do I activate it? The setting in the ui is turned on. |
You can enable catching by allowing a higher TTL in your DNA settings. |
📑 I have found these related issues/pull requests
None
🛡️ Security Policy
Description
I'm getting a very very high amount of dns traffic because of uptime kuma, as it queries dns every 60 seconds for hundreds of domains, could you fix that by adding some sort of cache?
👟 Reproduction steps
Add a good amount of https domains, leave scrape time at default
👀 Expected behavior
Very little dns traffic, possibly once an hour, this would remove 60x dns traffix
😓 Actual Behavior
Every 60 seconds my dns server get's flooded with requests
🐻 Uptime-Kuma Version
1.23.11
💻 Operating System and Arch
I run Arch btw.
🌐 Browser
Google Chrome 124.0.6367.61
🖥️ Deployment Environment
tteck's helper scripts via LXC on proxmox: https://tteck.github.io/Proxmox/
📝 Relevant log output
No response
The text was updated successfully, but these errors were encountered: