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.