advancedTop 100 Interview Questions
Why doesn't the default Docker bridge network support container-name-based DNS resolution?
The default bridge network predates Docker's embedded DNS server feature and was never upgraded with that capability for backward-compatibility reasons; only user-defined bridge networks (created via `docker network create` or implicitly by Compose) get automatic name-based service discovery.
Ready to master this question?
Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.
Sign in to generate a response