Issue with docker-compose networking on Windows -- Can't resolve service names

I'm running a Docker Compose setup with three services (web, api, redis) and the web container can't reach the api via its service name — DNS resolution is failing even though both are in the same network. I've tried: restarting docker desktop, creating a custom bridge network explicitly, adding --network host to the compose file, and rebuilding with --no-cache. Still getting "could not resolve api" errors on connection attempts from web -> api. Is there a common Docker Desktop for Windows networking bug I should check first?