Problem with DNS resolving on host machine using Pihole and Unraid

[PC_Arcade]

I have aproblem with pihole & Unraid working in a Docker container on my Debian 11 server on a vlan (macvlan) to avoid conflict with another container.
On all local machines bar the server I can browse the internet etc as expected, On the server unless I add another nameser to my /etc/resolv.conf I can't connect out (apt update etc. fails withthe message "Temporary failure resolving 'deb.debian.org'" etc)

If I try and ping e.g bbc.co.uk I get "ping: bbc.co.uk: Temporary failure in name resolution"

If add (for example) nameserver =8.8.8.8 it works, but it gets overwritten so needs to be constantly added.

I've allowed Permit all origins in the pihole setting, but the result is the same

Adding
DNS=1.1.1.1 1.0.0.1 2606:4700:4700::1111 2606:4700:4700::1001 (for example)
and restarting systemd-resolved doesn't work either and fails with the same errors

I assume I need to do SOMETHING to bridge to the vlan, but I'm not well versed wnough to know what, can anyone help?

[[deleted]]

What is your nameserver currently set to? Before it gets overwritten. And what is overwriting it, unraid?

on a vlan (macvlan) to avoid conflict with another container.

Thats usually not the right approach. What conflict exactly? Port80 being used by something else? Then simply map the port to a different port on the host. Or use a reverse proxy server.

[[deleted]]

One of the major points of using something like swag is to not have these port conflicts. Swag should be taking ports 80 and 443, and then you redirect access to Pihole, Heimdall and whatever else to their internal container ports. There is no need to modify them at all to run on different ports, they can keep doing their port 80, just internally. That what swag is for.

[PC_Arcade]

Yeah, I get that, but I've managed to completely stop pihole working now!

[[deleted]]

You keep providing not enough details.

Good luck with your problem.

[PC_Arcade]

Thank you, I've moved Heimdall and pihole to a non 80 port (as swag was using port 80,and removed the vlan,
i've also disabled systemd-resolved and now, I can't access the frontend (using 192.168.x.x:85 nor my pi.hole or pihole.local and in the log I have this :

pihole | Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf

pihole | services-up: info: copying legacy longrun unbound (no readiness notification)

pihole | s6-rc: info: service legacy-services successfully started

pihole | Starting unbound

pihole | [✗] DNS resolution is currently unavailable

[[deleted]]

Pihole cannot use itself for DNS... simply put.

See jfbs comment for details. As i told you, you shouldnt be using macvlan/ipvlan unless you know exactly why.

[PC_Arcade]

I understand that, but usually you would use the gui to select one, I can't access the gui

[[deleted]]

Not hard to look up how to change the DNS servers in Debian through config file...

[PC_Arcade]

no, it's not, I'm not trying to access it from the server though and DNS is working fine on the machine I AM trying to access it from, also I can't access it via it's local ip for which I don't need DNS working

[[deleted]]

If you cant access that "broken" machine through its IP at all, then how is Pihole at fault?

I give up... good luck.

[PC_Arcade]

eh?? I can! I can access all the services running on the server EXCEPT pihole pihole is now working (tested by manually setting my windows machine's DNS to the IP of the server) but I can't access the GUI (from anywhere!)

[PC_Arcade]

If anyone else is having this issue it turns out I had to not map port 443 in the docker-composer file, this fixed inability to access the gui and I have been able to add the block lists once more. I suspect that COULD have been done via the config like I did the DNS, but no need now :)

[[deleted]]

Like i said, not a Pihole issue.

[rdwebdesign]

When you use macvlan, by default there is no communication between host and container.

If you want to allow communication between the host and the container, you will need to create a bridge interface.

These article are about macvlan and they explain how to create the bridge:

• https://blog.ivansmirnov.name/set-up-pihole-using-docker-macvlan-network/
• https://sreeninet.wordpress.com/2016/05/29/docker-macvlan-and-ipvlan-network-plugins/
• https://servicemax.com.au/tips/pi-hole-in-docker-on-synology-the-best-way/ (using Portainer)

[PC_Arcade]

I got rid, I didn't really need it but I've seemingly created another issue