Skip to content

Domains not Blocking by Group/Client #2766

@awbl00

Description

@awbl00

Versions

  • Pi-hole: 6.3
  • Web: 6.4
  • FTL: 6.4.1

Platform

  • OS and version: Debian 11
  • Platform: VirtualBox VM

Expected behavior

RegEx domains added as deny and assigned to a group other than default will be blocked for all clients belonging to that group. This would apply to clients identified solely by name where pi-hole utilizes a custom DNS server, and all clients are identified via reverse lookup to the custom server.

Actual behavior / bug

Domains set for deny are blocked when assigned to the Default group but are allowed if assigned to any other group.

Steps to reproduce

Steps to reproduce the behavior:

  1. Create a new Group
  2. Create a regex domain set for deny and assign to the group created in step 1
  3. Create a client identified solely by name (e.g., phone-client.home) and assign to the group created in step 1. Ensure this client name is resolvable by Pi-Hole via reverse DNS lookup and that the client is using Pi-Hole for all DNS lookups.
  4. From the client, attempt to access the domain configured in step 2. The domain will still be accessible

Debug Token

  • URL:

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Clients are being properly identified by the fact that the client names are visible in the query log. Also, blocking works as expected if utilizing the default group instead of a custom group.

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