Dynamic DNS lookups stopped working for me after upgrading from 1.6.4 to 1.6.5 on up-to-date RHEL6 . There are no messages about server address change in syslog and when tcpdumping tcp/udp port 53, I do not see periodical DNS questions. Downgrading to 1.6.4 mages everything working again.
My servers using dynamic resolution are basically configured like this:
global
log 127.0.0.1 local6 debug
chroot /var/lib/haproxy
pidfile /var/run/haproxy.pid
maxconn 4000
user haproxy
group haproxy
external-check
daemon
# turn on stats unix socket
stats socket /var/lib/haproxy/stats user zabbix
node node-02
log-send-hostname node-02.example.com
Thanks for your answer. It appears that your patch makes dynamic DNS resolution in 1.6.5 working again.
But one more question. 1.6.5 is declared as important and suggested update, but now we know that it also contains at least one bug that has significant impact when used with my configuration. So the question is: Which version should I use for production?
stay with 1.6.4
use 1.6.5 with your patch
use the latest 1.6 with post-1.6.5 commits from git
If you are not impacted by the bugs in 1.6.4 I would suggest to stick with that for the moment.
If you need the 1.6.5 bugfixes, my suggestion would be to use 1.6.5 with my patch.
But more importantly I would say use the method you are most comfortable with.
Think we’ve hit the same problem using latest Docker image. Are we expecting a 1.6.6 release soon or is downgrading to 1.6.4 advised for the next few weeks?
Hi, http://blog.haproxy.com/2015/10/14/whats-new-in-haproxy-1-6/ under “Server IP Resolution…” does not show a FQDN - we are in the same scenario using Docker with container-names across user-defined networks. I may be missing some precise detail not shown of course…