Hey Simon,
when setting up a new docker server this morning I desperately
missed the specify-server-by-host feature in dnsmasq. I revived
my initial patch and added what was requested: I removed the
compile-time option and changed the code to always use all
suitable addresses (IPv6 is not
On Thu, Apr 07, 2022 at 05:27:31PM +0200, Geert Stappers via Dnsmasq-discuss
wrote:
> On Thu, Apr 07, 2022 at 12:24:15PM +0100, Simon Kelley wrote:
> > This seems like a sensible idea, but it does need a clear warning in the
> > documentation that it will only work if the dnsmasq instance being
>
On Thu, Apr 07, 2022 at 12:24:15PM +0100, Simon Kelley wrote:
> This seems like a sensible idea, but it does need a clear warning in the
> documentation that it will only work if the dnsmasq instance being
> configured is not the one providing DNS to the local system.
And the idea did trigger
This seems like a sensible idea, but it does need a clear warning in the
documentation that it will only work if the dnsmasq instance being
configured is not the one providing DNS to the local system.
Two comments about the patch.
1) Geert's point is a good one: This patch uses only libc: it
On Sat, Apr 02, 2022 at 09:40:15PM +0200, Dominik Derigs wrote:
> Dear Simon,
Dear Mailinglist audience,
(both the direct readers and the archive vistors)
> In docker swarm and compose configurations, other containers are
> only reachable via hostnames. It is not always possible to assign
> IP
Dear Simon,
In docker swarm and compose configurations, other containers are
only reachable via hostnames. It is not always possible to assign
IP addresses beforehand. Hence, the upstream server IP is not
known at dnsmasq start when the upstream is part of the deployed
configuration, e.g., a
