container unable to resolve dns properly

[xamindar]

This is a: BUG

Details

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: Rasbian,Arch,k3s
• Hardware: raspberry pi4 and intel x86_64
• Kernel Architecture: amd64 and arm64
• Docker Install Info and version:
  • Software source: k3s - v1.27.6+k3s1
  • Supplimentary Software:
• Hardware architecture: amd64 and arm64 (mixed arch cluster)

2. docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here
3. any additional info to help reproduce
   pihole containers have same /etc/resolv.conf as any other container in my cluster (internal cluster dns), however, it is unable to ping simple external domains because it tacks on the search domain to everything.
   -If I ping, for example, "ping google.com." with a dot at the end it works, no dot - it fails.
   -If I comment out the search line, external dns resolution starts working

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)
• I have tried a newer or older version of Docker Pi-hole (depending what version the issue started in for me)
  (older versions, v5, work fine)
• I have tried running without my volume data mounts to eliminate volumes as the cause

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]

Please provide a debug token and your docker compose file

[xamindar]

I found a workaround in setting the "ndots" option in resolv.conf to 1 instead of the default of 5. Still some issue with this container, but I'm going to assume it will be closed as a "wont fix" due to me using k8s instead of docker compose.
Let me know if you do want more info and I will put in more effort.
Thanks.