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

DNS not changing on Fedora Atomic Desktops #8

Open
4 tasks done
ghost opened this issue Oct 6, 2024 · 2 comments
Open
4 tasks done

DNS not changing on Fedora Atomic Desktops #8

ghost opened this issue Oct 6, 2024 · 2 comments

Comments

@ghost
Copy link

ghost commented Oct 6, 2024

Prerequisites

  • I have checked the Knowledge Base and the Discussions and found no answer

  • I have searched other issues and found no duplicates

  • I want to report a bug and not ask a question or ask for help

  • I have set up AdGuard DNS Clients correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)

Platform (OS and CPU architecture)

Linux, AMD64 (aka x86_64)

Installation

GitHub releases

Setup

On a personal machine

AdGuard DNS Client version

0.0.1

Action

  1. Install client following install instructions
  2. Check detected DNS on AdGuard DNS dashboard

Expected result

DNS showing as the client that it was setup as in the AdGuard DNS dashboard.

Actual result

Upstream DNS shown instead of set DNS server within the config, after restarting the AdGuard DNS Client.

Additional information and/or screenshots

OS: Fedora Onyx 40 Atomic Desktop
DE: Budgie 10.9.2
VM: VMWare Fusion Professional Version 13.6.0 (24238079)

@ghost
Copy link
Author

ghost commented Oct 28, 2024

Same issue with Fedora 40 Workstation, and Fedora 41 Workstation.

@Chinaski1
Copy link
Member

Hello there!

If I understand you correctly are you want to make client as a system resolver after installation?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant