Upstream for specific client doesn’t work #3210

Closed
opened 2026-03-04 03:12:09 -05:00 by deekerman · 3 comments
Owner

Originally created by @optimusleobear on GitHub (Nov 23, 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

Originally created by @optimusleobear on GitHub (Nov 23, 2021). ### Prerequisites Please answer the following questions for yourself before submitting an issue. **YOU MAY DELETE THE PREREQUISITES SECTION.** - [x] I am running the latest version - [x] I checked the documentation and found no answer - [x] I checked to make sure that this issue has not already been filed ### Issue Details <!-- Please include all relevant details about the environment you experienced the bug in. If possible, include the result of running `./AdGuardHome -v --version` from the installation directory. --> * **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](https://user-images.githubusercontent.com/33143885/143169895-4d0fe77b-da1e-4767-b4b3-8a26541233b0.jpeg) ![39DD6F2E-0BDD-46C3-99FB-C6778E4CD579](https://user-images.githubusercontent.com/33143885/143169913-18334824-08b6-4d5c-bca4-eeb519570e4f.jpeg) ### Additional Information <!-- Add any other context about the problem here. -->
deekerman 2026-03-04 03:12:09 -05:00
  • closed this issue
  • added the
    wontfix
    label
Author
Owner

@agneevX commented on GitHub (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.

@agneevX commented on GitHub (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.
Author
Owner

@ainar-g commented on GitHub (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 commented on GitHub (Nov 24, 2021): Sounds like a dup of #3186. @optimusleobear, could you please check if the latest beta releases fix the issue for you?
Author
Owner

@stale[bot] commented on GitHub (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[bot] commented on GitHub (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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/AdGuardHome#3210
No description provided.