Not responding to DNS queries (from local network)

[zambrinf]

Versions

Core version is v6.0 (Latest: v6.0)
Web version is v6.0 (Latest: v6.0)
FTL version is vDev-eaa7dbb (Latest: v6.0)

Platform

• OS and version: Debian GNU/Linux 12

• Platform: raspberry pi

Expected behavior

Dns queries working in my local network

Actual behavior / bug

Being blocked by pihole as if it was non-local

Steps to reproduce

Steps to reproduce the behavior:

• Had docker running version 2024.07.0
• Updated to latest
• try nslookup google.com <masked ip> from another machine (local)

DNS request timed out.
    timeout was 2 seconds.
Servidor:  UnKnown
Address:  <masked ip>

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** O tempo limite da solicitação para UnKnown expirou

Debug:
https://tricorder.pi-hole.net/OOL8jTA6/

*** [ DIAGNOSING ]: Pi-hole diagnosis messages
   count   last timestamp       type                  message                                                       blob1                 blob2                 blob3                 blob4                 blob5

   ------  -------------------  --------------------  ------------------------------------------------------------  --------------------  --------------------  --------------------  --------------------  --------------------
   1       2025-02-18 18:48:08  DNSMASQ_WARN          ignoring query from non-local network <masked ip>(logged

                                                       only once)

[rdwebdesign]

Please, provide a Debug Token.

[zambrinf]

@rdwebdesign
https://tricorder.pi-hole.net/OOL8jTA6/

[PromoFaux]

@zambrinf - what does your docker run/compose look like please?

[zambrinf]

@PromoFaux

services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    ports:
      - "53:53/tcp"
      - "53:53/udp"
    expose:
      - "80/tcp"
    environment:
      TZ: 'America/Sao_Paulo'
    volumes:
      - './etc-pihole:/etc/pihole'
      - './etc-dnsmasq.d:/etc/dnsmasq.d'
    restart: unless-stopped
    networks:
      - homelab1

networks:
  homelab1:
    name: homelab
    external: true

That network is a bridge one

[PromoFaux]

Can you try setting dns.ListeningMode in the settings to Single?

Either through the web interface, or by adding FTLCONF_dns_listeningMode: 'SINGLE' to the environment section of your compose file

[zambrinf]

Using FTLCONF_dns_listeningMode: 'SINGLE' works, DNSMASQ_LISTENING: 'SINGLE' doesn't work

[zambrinf]

I think I might have changed it manually sometime and it got "reset" with the new version

[PromoFaux]

DNSMASQ_LISTENING: 'SINGLE' doesn't work

I didn't say to try this? Or did you have that set before and it didn't work, so you removed it?

From the announcement blog post:

The docker image has undergone a complete rewrite from the ground up, and is now based on Alpine rather than Debian. The same migration scripts that run on bare metal will also run on Docker – your configurations will be migrated to the new format.

The exception to this is environment variables. You can start the container with the old variables in place but don’t expect them to work! It is recommended to read the docker section of our docs page before upgrading.

[zambrinf]

@PromoFaux No, just saying cause I was looking for a solution and in DockerHub it suggests to use DNSMASQ_LISTENING env variable, I also tried that and didn't work

[PromoFaux]

Wheeee, thanks - I need to update that page!

[PromoFaux]

All updated. Thanks for the reminder. So does setting that config option solve your issue?

[zambrinf]

yep, but was kinda strange that it reset my old config, it's good to have this issue for someone to check later