Update HAProxy's Invalid Address

[WistfulAdris]

It looks like few websites are no longer resolving to the address stated below -- which causes the fetal error on the HAProxy initialization. This is simple fix: simply remove or comment out the lines containing 'server atv.amazon.com, 'ptest.verdandi.is' and it should be functional once more.

[ALERT] 065/030135 (25328) : parsing [/etc/haproxy/haproxy.cfg:329] : 'server atv.amazon.com' : invalid address: 'atv.amazon.com' in 'atv.amazon.com:80'

[ALERT] 065/030135 (25328) : parsing [/etc/haproxy/haproxy.cfg:542] : 'server ptest.verdandi.is' : invalid address: 'ptest.verdandi.is' in 'ptest.verdandi.is:80'

[ALERT] 065/030135 (25328) : parsing [/etc/haproxy/haproxy.cfg:829] : 'server atv.amazon.com' : invalid address: 'atv.amazon.com' in 'atv.amazon.com:443'

[ALERT] 065/030135 (25328) : parsing [/etc/haproxy/haproxy.cfg:1015] : 'server ptest.verdandi.is' : invalid address: 'ptest.verdandi.is' in 'ptest.verdandi.is:443'

[lostC12138]

https://discourse.haproxy.org/t/haproxy-fails-to-start-if-backend-server-names-dont-resolve/322/28
may this helpful
haproxy-1.7.x and higher suppot init-addr configuration