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

Upstream for specific client doesn’t work #3872

Closed
3 tasks done
optimusleobear opened this issue Nov 24, 2021 · 3 comments
Closed
3 tasks done

Upstream for specific client doesn’t work #3872

optimusleobear opened this issue Nov 24, 2021 · 3 comments
Labels

Comments

@optimusleobear
Copy link

optimusleobear commented Nov 24, 2021

Prerequisites

Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

  • I am running the latest version
  • I checked the documentation and found no answer
  • I checked to make sure that this issue has not already been filed

Issue Details

  • Version of AdGuard Home server:
    • v0.106.3
  • How did you install AdGuard Home:
    • GitHub install script
  • How did you setup DNS configuration:
    • Ubuntu on AWS
  • CPU architecture:
    • AMD 64
  • Operating system and version:
    • Ubuntu 20.04

Expected Behavior

I have set upstream DNS server for specific client, so the client should use that.

Actual Behavior

All the clients are still using the global upstream DNS server in spite of the client settings.

Screenshots

D64119B0-157C-4776-BF50-465492597DF2
39DD6F2E-0BDD-46C3-99FB-C6778E4CD579

Additional Information

@agneevX
Copy link
Contributor

agneevX commented Nov 24, 2021

Since the server used is in fact specified in the client's settings, I think it uses the default Load-balancing setting.

@ainar-g
Copy link
Contributor

ainar-g commented Nov 24, 2021

Sounds like a dup of #3186. @optimusleobear, could you please check if the latest beta releases fix the issue for you?

@ainar-g ainar-g added the waiting for data Waiting for users to provide more data. label Nov 24, 2021
@stale
Copy link

stale bot commented Mar 2, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Mar 2, 2022
@stale stale bot closed this as completed Apr 16, 2022
@ainar-g ainar-g removed the waiting for data Waiting for users to provide more data. label Apr 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants