Re: Issue with parsing DNS from AWS

Thanks for the update. We will see what we can do, and I appreciate your help! Jim From: Baptiste Sent: Thursday, July 12, 2018 8:59:53 AM To: Jim Deville Cc: haproxy@formilux.org; Jonathan Works Subject: Re: Issue with parsing DNS from AWS Hi Jim, "

Re: Issue with parsing DNS from AWS

them work as well. > > > Jim > -- > *From:* Baptiste > *Sent:* Tuesday, July 3, 2018 9:20:53 AM > > *To:* Jim Deville > *Cc:* haproxy@formilux.org; Jonathan Works > *Subject:* Re: Issue with parsing DNS from AWS > > Ah yes, I also added

Re: Issue with parsing DNS from AWS

Sent: Tuesday, July 3, 2018 9:20:53 AM To: Jim Deville Cc: haproxy@formilux.org; Jonathan Works Subject: Re: Issue with parsing DNS from AWS Ah yes, I also added the following "init-addr none" statement on the server-template line. This prevents HAProxy from using libc resolvers, which

Re: Issue with parsing DNS from AWS

;> 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 Dev

Re: Issue with parsing DNS from AWS

, 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 >> > wrote: >>> >>>> Hi Bapiste, >>>> >>&

Re: Issue with parsing DNS from AWS

pro and perhaps >>> had a patch we could try? >>> >>> >>> Jim >>> -- >>> *From:* Jim Deville >>> *Sent:* Thursday, June 21, 2018 1:05:49 PM >>> *To:* Baptiste >>> *Cc:* haproxy@formilux.org; J

Re: Issue with parsing DNS from AWS

>> >> 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:* Bapti

Re: Issue with parsing DNS from AWS

-- > *From:* Jim Deville > *Sent:* Thursday, June 21, 2018 1:05:49 PM > *To:* Baptiste > *Cc:* haproxy@formilux.org; Jonathan Works > *Subject:* Re: Issue with parsing DNS from AWS > > > Thanks for the reply, we were able to extract a minimal repro to >

Re: Issue with parsing DNS from AWS

ts it at the subnet's +2). Jim From: Baptiste Sent: Thursday, June 21, 2018 11:02:26 AM To: Jim Deville Cc: haproxy@formilux.org; 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 fin

Re: Issue with parsing DNS from AWS

t the subnet's +2). Jim From: Baptiste Sent: Thursday, June 21, 2018 11:02:26 AM To: Jim Deville Cc: haproxy@formilux.org; 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

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

Re: Issue with parsing DNS from AWS

gt; environment to confirm a fix if this is a bug as it seems. > > > Jim > > -- > *From:* Jim Deville > *Sent:* Tuesday, June 19, 2018 6:00:07 PM > *To:* haproxy@formilux.org > *Cc:* Jonathan Works > *Subject:* Issue with parsing DNS from AWS

Re: Issue with parsing DNS from AWS

Jim From: Jim Deville Sent: Tuesday, June 19, 2018 6:00:07 PM To: haproxy@formilux.org Cc: Jonathan Works Subject: Issue with parsing DNS from AWS We have a setup with ECS and AWS's Service Discovery being load balanced by HAProxy in order to support sticky sessions for WebSocket handshakes,

Issue with parsing DNS from AWS

We have a setup with ECS and AWS's Service Discovery being load balanced by HAProxy in order to support sticky sessions for WebSocket handshakes, and we're working on making it more efficient by upgrading to 1.8.9 and taking advantage of seamless reloads and DNS service discovery. We have a solu