Rob Murray c3af3de173 A '--dns' server will not be replaced by default DNS ...

Google's DNS servers are currently used by containers on the default
bridge network, when none of the host's /etc/resolv.conf nameservers
are usable (host loopback addresses that the container can't see).

But, if a server is supplied via the --dns option, it'll just appear
in the container's resolv.conf (on the default bridge) or as an
upstream server for the internal resolver.

So, fix the networking-intro page's description, noting that requests
to --dns servers happen in the container's namespace.

Signed-off-by: Rob Murray <rob.murray@docker.com>

2024-05-16 12:25:49 +01:00

..

drivers

Merge pull request #19833 from dvdksn/com.docker.network.bridge.inhibit_ipv4

2024-04-24 22:32:56 +02:00

_index.md

A '--dns' server will not be replaced by default DNS

2024-05-16 12:25:49 +01:00

links.md

Engdocs 1938 tier1 (#19068)

2024-01-11 08:19:40 +00:00

network-tutorial-host.md

Update docs for host networking (#19783)

2024-04-11 10:27:31 +01:00

network-tutorial-macvlan.md

lint: enable markdownlint MD022 / blanks-around-headings

2024-04-17 09:36:28 +02:00

network-tutorial-overlay.md

network: remove bridge tutorial from overlay page

2024-02-21 12:17:35 +01:00

network-tutorial-standalone.md

Engdocs 1938 tier1 (#19068)

2024-01-11 08:19:40 +00:00

packet-filtering-firewalls.md

network: disambiguate which program the iptables option applies to

2024-04-22 14:31:41 +02:00

proxy.md

cli: change reference docs url paths

2024-02-21 10:25:53 +01:00