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

Parental control and safe browsing options cause SERVFAIL in the responses and are not working #6181

Closed
4 tasks done
Versty opened this issue Sep 8, 2023 · 3 comments
Closed
4 tasks done
Assignees
Milestone

Comments

@Versty
Copy link

Versty commented Sep 8, 2023

Prerequisites

Platform (OS and CPU architecture)

Linux, AMD64 (aka x86_64)

Installation

GitHub releases or script from README

Setup

On one machine

AdGuard Home version

v0.107.37

Action

  1. Install and configure AdGuard Home
  2. Enable parental control option
  3. Launch terminal and perform nslookup xxnx.com command

Expected result

The IP address of AdGuard's protection page is displayed in response
The adult website is marked as blocked by parental control in the query log.

Actual result

The SERVFAIL error is displayed in the response section.
The adult website is marked as blocked by parental control in the query log.

Additional information and/or screenshots

parental_block_host: "" and safebrowsing_block_host: "" fields are empty in the default AdGuardHome.yaml config file.

@Versty Versty added the bug label Sep 8, 2023
@ainar-g ainar-g self-assigned this Sep 8, 2023
@ainar-g ainar-g pinned this issue Sep 8, 2023
@ainar-g ainar-g added this to the v0.107.38 milestone Sep 8, 2023
@ainar-g
Copy link
Contributor

ainar-g commented Sep 8, 2023

Working on a fix.

The workaround is to:

  1. Stop AdGuard Home.

  2. Edit the configuration file, AdGuardHome.yaml, to have:

    #
    filtering:
      #
      parental_block_host: 'family-block.dns.adguard.com'
      safebrowsing_block_host: 'standard-block.dns.adguard.com'
      #
  3. Start AdGuard Home.

adguard pushed a commit that referenced this issue Sep 8, 2023
Updates #6181.

Squashed commit of the following:

commit 3c4d0fe
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date:   Fri Sep 8 14:23:13 2023 +0300

    home: fix default safe browsing, parental
@ainar-g
Copy link
Contributor

ainar-g commented Sep 8, 2023

Should be fixed on Edge, going to be released with v0.107.38.

@ainar-g ainar-g closed this as completed Sep 8, 2023
@ainar-g ainar-g modified the milestones: v0.107.39, v0.107.38 Sep 11, 2023
@ainar-g ainar-g unpinned this issue Sep 13, 2023
@djparus
Copy link

djparus commented Sep 14, 2023

Working on a fix.

The workaround is to:

  1. Stop AdGuard Home.
  2. Edit the configuration file, AdGuardHome.yaml, to have:
    #
    filtering:
      #
      parental_block_host: 'family-block.dns.adguard.com'
      safebrowsing_block_host: 'standard-block.dns.adguard.com'
      #
  3. Start AdGuard Home.

This does not work. AdGuard Home v.0.107.38 on Keenetic Ultra

annguyen0 pushed a commit to annguyen0/AdGuardHome that referenced this issue Nov 27, 2023
Updates AdguardTeam#6181.

Squashed commit of the following:

commit 3c4d0fe
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date:   Fri Sep 8 14:23:13 2023 +0300

    home: fix default safe browsing, parental
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants