title: Haproxy 1.6.2 not recognizing resolvers section
body: <p>As a test, I have a local bind instance running:</p>
  
  <pre><code>&gt;netstat -ant | grep LISTEN
  tcp        0      0 10.72.186.23:53         0.0.0.0:*               LISTEN
  tcp        0      0 127.0.0.1:53            0.0.0.0:*               LISTEN
  ...
  
  &gt;nslookup mysubdomain.example.com 127.0.0.1
  Server:     127.0.0.1
  Address:    127.0.0.1#53
  
  Name:   mysubdomain.example.com
  Address: nn.nn.nn.251
  Name:   mysubdomain.example.com
  Address: nn.nn.nn.249
  Name:   mysubdomain.example.com
  Address: nn.nn.nn.201
  Name:   mysubdomain.example.com
  Address: nn.nn.nn.138
  </code></pre>
  
  <p>I'm running haproxy 1.6.2 on the same host, with a resolvers section:</p>
  
  <pre><code>resolvers dns
      nameserver dns1 127.0.0.1:53
      nameserver dns2 10.72.186.23:53
      hold valid 10s
  </code></pre>
  
  <p>It doesn't reject the resolvers section, but doesn't seem to be using it, either. It doesn't show in the stats page, and attempting to add this service command:</p>
  
  <pre><code>server mysubdomain-dev mysubdomain.example.com
  </code></pre>
  
  <p>causes this error:</p>
  
  <pre><code>&gt;service haproxy restart
   * Restarting haproxy haproxy
  [ALERT] 322/171813 (10166) : parsing [/etc/haproxy/haproxy.cfg:77] : 'server mysubdomain-dev' : invalid address: 'mysubdomain.example.com' in 'mysubdomain.example.com'
  [ALERT] 322/165300 (29751) : Error(s) found in configuration file : /etc/haproxy/haproxy.cfg
  [ALERT] 322/165300 (29751) : Fatal errors found in configuration.
  </code></pre>
  
  <p>The haproxy doc <a href="https://cbonte.github.io/haproxy-dconv/configuration-1.6.html" rel="nofollow">https://cbonte.github.io/haproxy-dconv/configuration-1.6.html</a> indicates this should work.</p>
  
  <p>server &lt;name&gt; &lt;address&gt;[:[port]] [param*]</p>
  
  <p>...</p>
  
  <p>&lt;address&gt; is the IPv4 or IPv6 address of the server. Alternatively, a
            resolvable hostname is supported, but this name will be resolved
            during start-up. Address "0.0.0.0" or "*" has a special meaning.</p>
  
  <p>Is there some other piece that needs to be added to the haproxy.cfg that activates the resolvers section?</p>