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

Access setup issues #3299

Closed
carrot-eggs opened this issue Jun 29, 2021 · 2 comments
Closed

Access setup issues #3299

carrot-eggs opened this issue Jun 29, 2021 · 2 comments
Labels
duplicate Duplicate or merged issues.

Comments

@carrot-eggs
Copy link

hi,Customizing the upstream through the client ID cannot take effect, and it will still be resolved through the upstream DNS set globally, as shown in the figure:
图片
图片
图片
图片
My adguardhome is installed on a VPS, and I cannot set up a dedicated upstream DNS for a certain device through the client ID.
adguardhome version: v0.106.3

@ainar-g
Copy link
Contributor

ainar-g commented Jun 29, 2021

Hello again. This seems like something we've fixed in the main branch, in #3186. Can you install a beta version, say v0.107.0-b.3, and check if this issue is still there?

@ainar-g ainar-g added the waiting for data Waiting for users to provide more data. label Jun 29, 2021
@carrot-eggs
Copy link
Author

@ainar-g
Hi,
I upgraded to v0.107.0-b.3. After testing, I have been able to use custom upstream DNS through the client ID. The problem has been resolved.
Thank you for your support, and hope AdGuardHome gets better and better!

@ainar-g ainar-g added duplicate Duplicate or merged issues. and removed waiting for data Waiting for users to provide more data. labels Jun 30, 2021
@ainar-g ainar-g closed this as completed Jun 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Duplicate or merged issues.
Projects
None yet
Development

No branches or pull requests

2 participants