Prevent a non-working loop of Pi-Hole LXC pointing to itself for DNS

[mgrimace]

Hi folks, when using Pi-Hole LXC, what's the best way to prevent the LXC from using itself as it's own DNS provider? For example, if Proxmox is using the DNS settings from the router, which, in turn, point to the Pi-Hole, potentially creating a loop.

Would setting the LXC's DNS server as say 1.1.1.1 (Cloudflare) 'hardcode' it just for that particular LXC or does it use Proxmox's DNS server by default?

Hopefully that makes sense. And to clarify, I'm not speaking to the upstream server (e.g., unbound, DNScrypt-proxy, etc.) for Pi-Hole, I'm speaking to the LXC's DNS server, which shouldn't be itself.

[BramSuurdje]

When you configured the Pi-hole LXC and you did not change the DNS settings, the default DNS will follow the Proxmox host. So, setting the DNS server of the LXC to, for example, 1.1.1.1 or 8.8.8.8 will hardcode it to only the Pi-Hole LXC and will also prevent it from breaking as you mentioned.

[mgrimace]

Thanks, so even though 1.1.1.1 is hardcoded into the LXC is there then any conflict with the Proxmox host itself obtaining DNS from its own LXC (via the router->DHCP->LXC IP set as DNS)?