[documentation] Add description how to enable consul DNS in Docker containers when consul listens :8600 port

[EugenKon]

Proposal

I checked this solution and it works as expected. It would be nice if this will be added to official documentation here

[jrasell]

Hi @EugenKon, the proposed documentation to change links to the Consul site, is this expected or should this be a Nomad reference link?

[EugenKon]

Hi, @jrasell . It seems I do not understand your question about Nomad reference link.

[jrasell]

@EugenKon the final link in your description points to a Consul tutorial.

I checked #12894 (comment) solution and it works as expected. It would be nice if this will be added to official documentation here

[EugenKon]

Yes, it does.

[slonopotamus]

I believe people just want a clear explanation on how to configure Nomad+Consul so that docker tasks running in Nomad can utilize Consul DNS, regardless of whether it is documented in Nomad or Consul docs.

[EugenKon]

Ah, It seems I got. I mess up repositories. This issue should be opened in hashicorp/consul repository.

[EugenKon]

And I agree with @slonopotamus . People just need a clear description how to utilize Consul DNS for tasks running in Nomad. The link I have posted points to Consul documentation, because that is most close part of documentation to the topic. And it would be nice if that part could be improved.

[EugenKon]

My final solution is:
/etc/systemd/resolved.conf.d/dns.conf

[Resolve]
DNSSEC=false
DNS=127.0.0.1:8600

DNSStubListener=yes
DNSStubListenerExtra=172.17.42.1

Domains=~consul

/etc/docker/daemon.json

{
  "bip": "172.17.42.1/16",
  "dns-search": ["our.domain.example.com"],
  "dns": ["172.17.42.1"]
}

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.