Closed toffee closed 4 months ago
currently the dns forwarding flow is like below,
client => pihole => dnsmasq => dns_forward_ip_addresses
and dns_forward_ip_addresses
has a default value of [ "8.8.8.8", "8.8.4.4" ]
just change dns_forward_ip_addresses
to
dns_forward_ip_addresses: [ "<your_gateway_ip>" ]
in your env.yml and redeploy dnsmasq
my config is
dns_forward_ip_addresses: [ "{{default_server_gateway}}" ]
Thank you for your answer.
It's strange because my config was
dns_forward_ip_addresses: [ "{{default_server_gateway}}", "8.8.8.8", "8.8.4.4" ]
I removed now the google DNS IPs from my config. I will check to see if this behavior will be reproducible with next alpine update.
My ISP offer a parental control service (that I have it enabled). When this feature is enabled, I guess all DNS requests to other servers (like Google DNS 8.8.8.8) than local one are drop.
With parental control enabled on ISP side:
Without parental control enabled:
Sometimes the smartserver ansible scripts fail because of that. For example, now, when you updated the alpine version the creation of dnsmasq container failed. The names are not resolved because the 8.8.8.8 (that is used by docker) on 53 port is not accessible.
After I disabled the parental control on ISP then the ansible scripts works as expected.
It's nothing critical, but I just let you know - maybe there is an easy fix.
For the moment, my workarounds are: