From 09b3805d3bfe4e2d6aac06d5d19bcdd001190934 Mon Sep 17 00:00:00 2001
From: Dean Chen <862469039@qq.com>
Date: Tue, 11 Aug 2026 21:41:44 +0500
Subject: [PATCH 1/2] docs: note Google DNS fallback when host has no public
 resolvers

Document that dockerd falls back to 8.8.8.8/8.8.4.4 when resolv.conf
has only localhost nameservers, and that air-gapped hosts should set
--dns or daemon dns instead.

Fixes #22945

Signed-off-by: Dean Chen <862469039@qq.com>
---
 content/manuals/engine/network/_index.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/content/manuals/engine/network/_index.md b/content/manuals/engine/network/_index.md
index e68950cc595b..3473358beb83 100644
--- a/content/manuals/engine/network/_index.md
+++ b/content/manuals/engine/network/_index.md
@@ -259,6 +259,14 @@ override this with `--dns`.
 By default, containers inherit the DNS settings as defined in the
 `/etc/resolv.conf` configuration file.
 Containers that attach to the default `bridge` network receive a copy of this file.
+
+If the host's `resolv.conf` has no usable non-localhost nameservers (for example,
+only `127.0.0.1` or empty), the daemon falls back to Google Public DNS
+(`8.8.8.8` and `8.8.4.4`) for containers on the default bridge network and logs
+a message similar to `Using default external servers`. On air-gapped hosts this
+can make DNS lookups hang until those public resolvers time out. Override the
+fallback with `docker run --dns`, or set `"dns": [...]` in the daemon JSON
+configuration, when you need different or local resolvers.
 Containers that attach to a
 [custom network](drivers/bridge.md#use-user-defined-bridge-networks)
 use Docker's embedded DNS server.

From e9849548763f8f34155f902f826ed11566291967 Mon Sep 17 00:00:00 2001
From: Dean Chen <862469039@qq.com>
Date: Tue, 11 Aug 2026 23:31:07 +0500
Subject: [PATCH 2/2] chore: empty commit to retrigger CI

Signed-off-by: Dean Chen <862469039@qq.com>