search

Fallenbagel / jellyseerr

Fork of overseerr for jellyfin support.
https://docs.jellyseerr.dev/
MIT License
3.83k stars 244 forks source link

DNS Flooding to api.themoviedb.org #657

Closed Seimann closed 8 months ago

Seimann commented 8 months ago

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

Fallenbagel commented 8 months ago

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]

Seimann commented 8 months ago

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 commented 8 months ago

@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 commented 8 months ago

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 commented 8 months ago

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 commented 8 months ago

@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 commented 8 months ago

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

Fallenbagel commented 5 months ago

:tada: This issue has been resolved in version 1.9.1 :tada:

The release is available on:

Your semantic-release bot :package::rocket: