document 127.0.0.11

[qhaas]

Is this a docs issue?

• My issue is about the documentation content or website

Type of issue

I can't find what I'm looking for

Description

Mention of 127.0.0.11 as being an 'implicit ip' convenient for DNS configuration (e.g. in nginx) described in issue #1969 and added in pull 2822 does not seem to exist anymore. Several third-party guides, discussions, libnetwork tests, libnetwork source, etc. reference it, but I cannot find it specifically mentioned and described in the official documentation anymore.

Location

https://docs.docker.com/network/#dns-services

Suggestion

Document 127.0.0.11 as being an implicit DNS server IP

[dvdksn]

cc @robmry - I assume this is still applicable. Is there a corresponding ip6 address?

[robmry]

Yes, we still use 127.0.0.11.

There's no IPv6 equivalent, IPv4 loopback will always work (even in an IPv6-only container).

[docker-robot]

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

[thaJeztah]

@robmry anything to update here in the docs to mention our use of 127.0.0.11 as default for the embedded DNS resolver inside the container (on custom networks)?

[robmry]

I think we could mention it, there's no plan to change the address.

Something like https://github.com/docker/docs/pull/10019/files, but perhaps clarifying that it only applies to user-defined bridge networks (at least until buildkit can deal with an internal resolver on the default bridge and we re-do moby/moby#48020).