*I’m experiencing an issue where all DNS resolutions sent to dnsmasq
timeout, but only after the dnsmasq service has been successfully running
for a period of time (anecdotally, after a few weeks of time). After a lot
of digging, I’ve discovered that dnsmasq’s UDP socket file will eventually
“disap
of docker containers changed at any time? If so,
> forcing that is an obvious way of trying to reproduce this problem.
> Given that 127.0.0.1 is an address which dispappears, anything which
> fiddles with the lo interface is of particular suspicion.
>
>
>
> Cheers,
>
>
>
in output between a known working server and a failed server.
Your thought process did spark my interest in DHCP logs; however, the IP
address has been consistent throughout the issues.
Thanks,
Zach
On Tue, Feb 6, 2018 at 1:35 PM, Simon Kelley
wrote:
> On 05/02/18 15:43, Zi Dvbelju wr
