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

Site ICON lookup causing a DNS flood of requests to DNS server #3179

Open
1 task done
RonV42 opened this issue Aug 11, 2023 · 0 comments
Open
1 task done

Site ICON lookup causing a DNS flood of requests to DNS server #3179

RonV42 opened this issue Aug 11, 2023 · 0 comments
Labels
bug bw-unified-deploy An Issue related to Bitwarden unified deployment

Comments

@RonV42
Copy link

RonV42 commented Aug 11, 2023

Steps To Reproduce

  1. In Docker stop and restart container
  2. Open the Windows Desktop client
  3. As you scroll down the icons for the sites will start to fill
  4. My DNS server reports:
    RATE_LIMIT | Client 192.168.30.221 has been rate-limited (current config allows up to 1000 queries in 60 seconds)
  5. After the site icons stop filling and have a generic placeholder

Expected Result

I would expect that the ICON files should be cached locally not looked up when the Bitwarden container is started, and a client connects.

Actual Result

I would expect the ICONs to cache and be presented to the client vs a large block of DNS lookups to go to the site and pull the ICONs. There could be a Time to Live to refresh ICON's to keep them up to date.

Screenshots or Videos

No response

Additional Context

No response

Githash Version

2023.7.2

Environment Details

Server:
Operating System: Proxmox LXC container running Debian 12
Docker version 24.0.5, build ced0996

Client:
Windows 10 Pro Desktop Client
Version 2023.7.1
Shell 24.1.1
Renderer 112.0.5615.50
Node 18.14.0
Architecture x64

Database Image

image: mariadb:10

Issue-Link

#2480

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@RonV42 RonV42 added bug bw-unified-deploy An Issue related to Bitwarden unified deployment labels Aug 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug bw-unified-deploy An Issue related to Bitwarden unified deployment
Projects
None yet
Development

No branches or pull requests

1 participant