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

DNS Flooding to api.themoviedb.org #657

Closed
1 task done
Seimann opened this issue Feb 19, 2024 · 8 comments · Fixed by #810
Closed
1 task done

DNS Flooding to api.themoviedb.org #657

Seimann opened this issue Feb 19, 2024 · 8 comments · Fixed by #810
Labels

Comments

@Seimann
Copy link

Seimann commented Feb 19, 2024

Description

Why does Jellyseerr flood the DNS server with 12 requests every 4 seconds? (at any time of the day)
Look at this picture. 88.417 requests in ~one week!

jelly

All 88.417 entries are = api.themoviedb.org
That's really too much

Version

1.7.0 Stabil

Steps to Reproduce

Docker Installation on Unraid

Screenshots

No response

Logs

No response

Platform

desktop

Device

All

Operating System

Unraid

Browser

All

Additional Context

No response

Code of Conduct

  • I agree to follow Jellyseerr's Code of Conduct
@Fallenbagel
Copy link
Owner

Fallenbagel commented Feb 19, 2024

Duplicate of #387

Edit: as for the tmdb api, you're literally browsing and hitting the tmdb api for various different things. Either just ignore the tmdb api on adhuardhome/pihole or idk [what you want exactly]

@Fallenbagel Fallenbagel marked this as a duplicate of #387 Feb 19, 2024
@Seimann
Copy link
Author

Seimann commented Feb 19, 2024

Duplicate of #387

Edit: as for the tmdb api, you're literally browsing and hitting the tmdb api for various different things. Either just ignore the tmdb api on adhuardhome/pihole or idk [what you want exactly]

no, that's too many hits to "ignore" them
that should be solved

@JPVenson
Copy link

JPVenson commented Feb 19, 2024

@Seimann How would you solve this?
This is how the api is build and what your jellyseerr instance is requesting / its how you use it.
What did you expect Jellyseerr to work like? Imagine every bit of movie data? Ai? Magic?

@Fallenbagel
Copy link
Owner

Fallenbagel commented Feb 19, 2024

Like I said. It needs to be requested for all these operations. It already caches.

All the images are accessed directly as well. You can literally go to settings and turn on image proxy mode so all the images get cached, which will lower some of these requests.

Having a lot of dns requests is not an issue. There is nothing to be solved here....

@sevenrats
Copy link

the api uses a 24 second ttl. nothing jellyseerr can do about it.

------------
    QUESTIONS:
	api.themoviedb.org, type = A, class = IN
    ANSWERS:
    ->  api.themoviedb.org
	internet address = 18.245.96.44
	ttl = 24
    ->  api.themoviedb.org
	internet address = 18.245.96.97
	ttl = 24
    ->  api.themoviedb.org
	internet address = 18.245.96.110
	ttl = 24
    ->  api.themoviedb.org
	internet address = 18.245.96.52
	ttl = 24
    AUTHORITY RECORDS:
    ADDITIONAL RECORDS:
------------

@sevenrats
Copy link

@Seimann it took me this long to put together that 3 per second is more than 1 every 24 seconds. My guess is your DNS system is failing to honor the TTL properly. Jellyseerr is not the appropriate place for the fix.

@Seimann
Copy link
Author

Seimann commented Feb 19, 2024

Thanks for your information about TTL.
I solve the problem by ignoring the client from the AdGuard statistics

gauthier-th added a commit that referenced this issue Jun 1, 2024
gauthier-th added a commit that referenced this issue Jun 11, 2024
Fallenbagel pushed a commit that referenced this issue Jun 11, 2024
@Fallenbagel
Copy link
Owner

🎉 This issue has been resolved in version 1.9.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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