Hello every one,
I run consul services on my network where servics are registered with
xyz.service.consul when they start. All containers and bare metal hosts are
running dnsmasq 2.80.
I noticed that if I restart one of the containers one of the hosts continue
failing to resolve the server ho
On Sun, Jul 07, 2019 at 02:09:20PM -0500, Alex Litvak wrote:
> Hello every one,
>
> I run consul services on my network where servics are registered with
> xyz.service.consul when they start. All containers and bare metal hosts are
> running dnsmasq 2.80.
> I noticed that if I restart one of th
(luck of sleep, fixing some mistakes in text)
Hello everyone,
I run consul services on my network where services are registered with
.service.consul when they start. All containers and bare metal hosts are
running dnsmasq 2.80.
I noticed that if I restart one of the containers, one of the hos
Hello Alex,
I would try removing all-servers and clear-on-reload statements away. I
would use just one server for testing, retesting all of them for the
same behaviour. When you do not know which server is used, it is hard to
debug better.
I think dots in server=/.X/ are not necessary and maybe e
Petr,
Thank you very much for your help. I will follow your advice and report
my findings to the list.
On Wed, Jul 10, 2019, 4:47 AM Petr Mensik wrote:
> Hello Alex,
>
> I would try removing all-servers and clear-on-reload statements away. I
> would use just one server for testing, retesting
