Hi Jim, Sorry for the long pause :) I was dealing with some travel, conferences and catching up on my backlog. So, the good news, is that this issue is now my priority :)
I'll try to first reproduce it and come back to you if I have any issue during that step. (by the way, thanks for the github repo to help me speed up in that step). Baptiste On Mon, Jun 25, 2018 at 10:54 PM, Jim Deville <[email protected]> wrote: > Hi Bapiste, > > > I just wanted to follow up to see if you were able to repro and perhaps > had a patch we could try? > > > Jim > ------------------------------ > *From:* Jim Deville > *Sent:* Thursday, June 21, 2018 1:05:49 PM > *To:* Baptiste > *Cc:* [email protected]; Jonathan Works > *Subject:* Re: Issue with parsing DNS from AWS > > > Thanks for the reply, we were able to extract a minimal repro to > demonstrate the problem: https://github.com/jgworks/haproxy- > servicediscovery > > > The docker folder contains a version of the config we're using and a > startup script to determine the local private DNS zone (AWS puts it at the > subnet's +2). > > > Jim > ------------------------------ > *From:* Baptiste <[email protected]> > *Sent:* Thursday, June 21, 2018 11:02:26 AM > *To:* Jim Deville > *Cc:* [email protected]; Jonathan Works > *Subject:* Re: Issue with parsing DNS from AWS > > and by the way, I had a quick look at the pcap file and could not find > anything weird. > The function you're pointing seem to say there is not enough space to > store a server's dns name, but the allocated space is larger that your > current records. > > Baptiste >
