Skip to content

Commit dc39aa2

Browse files
authored
Merge pull request #25615 from dvdksn/codex/fix-7981-dns-resolver-behavior
docs: clarify multiple DNS server behavior
2 parents e57de8f + b792e25 commit dc39aa2

1 file changed

Lines changed: 9 additions & 0 deletions

File tree

content/manuals/engine/network/_index.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -267,6 +267,15 @@ The embedded DNS server address is `127.0.0.11`.
267267
There is no IPv6 equivalent; the IPv4 address works even in IPv6-only containers.
268268
If an application requires an explicit DNS server address, use `127.0.0.11`.
269269

270+
> [!NOTE]
271+
>
272+
> When you configure multiple DNS servers for a container on the default
273+
> `bridge` network, the container's resolver library determines how it queries
274+
> them. Some resolvers query the servers in order. Others query them in parallel
275+
> and use the first response received, even if that response is `NXDOMAIN`.
276+
> On a custom network, Docker's embedded DNS server queries upstream servers in
277+
> order and stops after a successful response or an `NXDOMAIN` response.
278+
270279
You can configure DNS resolution on a per-container basis, using flags for the
271280
`docker run` or `docker create` command used to start the container.
272281
The following table describes the available `docker run` flags related to DNS

0 commit comments

Comments
 (0)