Re: DNS resolution problem since 1.8.14

2018-12-25 Thread Willy Tarreau
Hi Patrick, On Mon, Dec 24, 2018 at 10:02:17AM +0100, Patrick Valsecchi wrote: > Hi Jonathan, > > I've build the 1.8.16 image myself and the problem is indeed fixed. Any plan > of including that fix in a 1.9.1 release? That's indeed planed, but as usual with any initial dot-zero release we've

Re: DNS resolution problem since 1.8.14

2018-12-24 Thread Patrick Valsecchi
Hi Jonathan, I've build the 1.8.16 image myself and the problem is indeed fixed. Any plan of including that fix in a 1.9.1 release? Thanks. On 23.12.18 18:20, Jonathan Matthews wrote: Hey Patrick, Have you looked at the fixes in 1.8.16? They sound kinda-sorta related to your problem ...

Re: DNS resolution problem since 1.8.14

2018-12-23 Thread Jonathan Matthews
Hey Patrick, Have you looked at the fixes in 1.8.16? They sound kinda-sorta related to your problem ... J On Sun, 23 Dec 2018 at 16:17, Patrick Valsecchi wrote: > I did a tcpdump. My config is modified to point to a local container (www) > in a docker compose (I'm trying to simplify my

Re: DNS resolution problem since 1.8.14

2018-12-23 Thread Patrick Valsecchi
I did a tcpdump. My config is modified to point to a local container (www) in a docker compose (I'm trying to simplify my setup). You can see the DNS answers correctly: 16:06:00.181533 IP (tos 0x0, ttl 64, id 63816, offset 0, flags [DF], proto UDP (17), length 68)     127.0.0.11.53 >