Skip to content

Why can't Adguard Home itself be the DNS server #4803

Closed
Closed
Why can't Adguard Home itself be the DNS server#4803

Description

@johndoe804
johndoe804
opened on Aug 3, 2022

Prerequisites

  • I have checked the Wiki and Discussions and found no answer

  • I have searched other issues and found no duplicates

  • I want to request a feature or enhancement and not ask a question

Description

What problem are you trying to solve?

Why can't Adguard Home itself be the DNS server?
Why rely on unbound or any other?

Proposed solution

Alternatives considered

Additional information

Activity

  1. fernvenue commented on Aug 4, 2022

    @fernvenue
    fernvenue
    on Aug 4, 2022
    Contributor

    As @ameshkov said in #3160:

    AdGuard is a DNS forwarder, not a recursor.

    That's why you must config some upstream servers in AdGuardHome.

    Regarding the recursor setup, if you are really sure that's what you need, consider running a local unbound instance and configure AGH to use it as an upstream. IMO, this does not provide any advantages, though. Mind that the queries that are made by a recursor are not encrypted so will be visible to your ISP.

    By the way, in addition to the disadvantages mentioned above, recursive queries usually have efficiency problems when used in small areas, each query will take a very long time.

  2. AdguardTeam
    locked and limited conversation to collaborators on Aug 22, 2022
  3. ainar-g
    converted this issue into a discussion #4858 on Aug 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions