I would like to use the FQDN of the consul nodes for various services unrelated to consul. A random example is when initialising kubernetes and connecting to the etcd cluster, which I’d like to do it using the DNS names instead of the IPs.
I guess the point is that whatever software it’s connecting to Consul is supposed to understand how Consul works. In my case it all (or most of it) goes down to dnsmasq, which redirects requests for company.internal to the consul internal DNS service (on port 8600).
So what I’m looking for is a suggestion of how I can achieve reaching these nodes using the FQDN (node-name.node.domain) or what are the ‘usual’ setups for that. I guess I don’t have the right overview.
There must be something I’m missing, it still doesn’t work, except for the node itself (dig A omni-consul-0.node.comp.internal @127.0.0.1 -p 8600) where I’m running the query (weirdly enough), but this works independently of the anonymous policy.