Missing documentation of Google DNS fallback 8.8.8.8 and 8.8.4.4
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- docker
- Domain
- documentation
Research direction
Start with the DNS services section of the networking chapter at the linked documentation location and review its existing DNS behavior coverage. Add a note explaining the fallback to 8.8.8.8 and 8.8.4.4 when no non-localhost DNS is configured, then verify the rendered documentation and wording.
Written by the indexing model from the issue text.
Description
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
Summary
Add a note to the documentation indicating that Docker falls back to Google DNS if no non-localhost DNS is defined.
Details
In one of my projects, I started a Docker container on a device without internet access and with no configured DNS other than localhost.
Inside the container, some DNS requests timed out after a long delay. I expected the DNS requests to fail immediately.
Upon checking the dockerd log, I found the following line during startup:
No non-localhost DNS nameservers are left in resolv.conf. Using default external servers: [nameserver 8.8.8.8 nameserver 8.8.4.4]
I reviewed the DNS section of the networking chapter, but found no mention of this behavior. I only discovered it referenced in another issue: https://github.com/moby/moby/issues/23910
Am I missing something?
Edit: Tested with Docker version 24.0.5, build ced0996
Location
https://docs.docker.com/engine/network/#dns-services
Suggestion
Maybe add a simple sentence to the chapter:
In case no non-localhost DNS is defined in the `/etc/resolve.conf`, a fallback to `8.8.8.8` and `8.8.4.4` will be added.
Exact formulation and placement is of course open for discussion.
- Dominant language
- Markdown
- Stars
- 4.7k
- Forks
- 8.5k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 104
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from docker/docs
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
status/triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
area/dhi status/triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100