Consul reports starting DNS on 8600, but nothing listening

Consul
1

I have a basic install of consul which is operating just fine over HTTP but not DNS.

/var/log/syslog shows the following:

consul[67513]:        Client Addr: [127.0.0.1] (HTTP: 8500, HTTPS: -1, gRPC: -1, DNS: 8600)
consul[67513]:     2020-05-11T21:17:42.622Z [INFO]  agent: Started DNS server: address=127.0.0.1:8600 network=udp
consul[67513]:     2020-05-11T21:17:42.622Z [INFO]  agent: Started DNS server: address=127.0.0.1:8600 network=tcp

But no process is listening on 8600. “ss -n | grep 8600” and “netstat | grep 8600” produces emtpy output, and the following command produces a connection refused error:

dig @127.0.0.1 8600 myservice.consul ANY

Any ideas as to what could be causing this to fail?

Config:

{
  "skip_leave_on_interrupt": true,
  "datacenter": "w",
  "limits": {
    "http_max_conns_per_client": 5000
  }
}

Command (redacted):

/usr/local/sbin/consul agent -data-dir=/var/lib/consul -config-dir=/etc/consul -bind=10.xx.xx.xx -retry-join=opstestw0.w-int.xx.xx -retry-join=opstestw1.w-int.xx.xx -retry-join=opstestw2.w-int.xx.xx -ui
2

Just some thoughts:

ss -n | grep 8600

This is empty on my system, too.
While this gives me the expected output:

netstat -pan | grep 8600

dig @127.0.0.1 8600 myservice.consul ANY

Is it just a typo, or is there an -p for port missing?

dig @127.0.0.1 -p 8600 myservice.consul ANY