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

Dnsmasq wildcard resolution works intermitently #1728

Closed
4 of 6 tasks
fabiodaa opened this issue Feb 20, 2025 · 1 comment
Closed
4 of 6 tasks

Dnsmasq wildcard resolution works intermitently #1728

fabiodaa opened this issue Feb 20, 2025 · 1 comment

Comments

@fabiodaa
Copy link

fabiodaa commented Feb 20, 2025

This is a: Bug

Details

After updating the docker image to v6, dnsmasq stopped working, so I come here and found that I had to activate misc.etc_dnsmasq_d and to update misc.dnsmasq_lines with address=/example.com/192.168.1.100, so I did it.
But dns resolution for that domain(not for others, works only intermitantly (most time not) and when not nslookup returns:
*** No internal type records for both IPv4 and IPv6 Addresses (A+AAAA) available for example.com
The main domain appears to work fine.

Related Issues

  • I have searched this repository/Pi-hole forums for existing issues and pull requests that look similar

How to reproduce the issue

  1. Environment data
  • Operating System: Raspberry pi os bookworm
  • Hardware: Raspberry pi 5 8 GB
  • Kernel Architecture: arm64
  • Docker Install Info and version:
    • Software source: official docker-ce
    • Supplimentary Software: no
  • Hardware architecture: armv8
  1. docker-compose.yml contents:
    version: "3"
    services:
    pihole:
    container_name: pihole
    image: pihole/pihole

    ports:

    • "53:53/tcp"
    • "53:53/udp"
    • "80:80/tcp"

    environment:
    TZ: "Europe/Madrid"
    volumes:

    • './config:/etc/pihole'
    • './25-nginx-domain.conf:/etc/lighttpd/conf-enabled/25-nginx-domain.conf'
      restart: unless-stopped
  2. any additional info to help reproduce

These common fixes didn't work for my issue

  • I have tried removing/destroying my container, and re-creating a new container
  • I have tried fresh volume data by backing up and moving/removing the old volume data
  • I have tried running the stock docker run example(s) in the readme (removing any customizations I added) (with this, the issue can't be reproduced)
  • I have tried a newer or older version of Docker Pi-hole (depending what version the issue started in for me) (with version 5.x, this doesn't happens)
  • I have tried running without my volume data mounts to eliminate volumes as the cause (with this, the issue can't be reproduced)

If the above debugging / fixes revealed any new information note it here.
Add any other debugging steps you've taken or theories on root cause that may help.

@yubiuser
Copy link
Member

Duplicate of #1718

Fixed with pi-hole/FTL#2204

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

2 participants