Container DNS & Discovery

Introduction

Docker runs an embedded DNS server on user-defined networks. Service names become hostnames — http://api:3000 just works without IPs or env vars.

Purpose of this lesson

This lesson teaches Container DNS & Discovery as an engineering decision: what problem it solves, when to use it, how to implement it safely, and what signals tell you it is failing.

Understanding the topic

Use this when containers must communicate, expose traffic, or persist state. Most real Docker incidents come from a wrong port, missing DNS name, unsafe bind mount, or data stored in the container writable layer.

Core concepts to understand:

• Embedded DNS at 127.0.0.11 inside containers.
• --name on bridge nets becomes the hostname.
• Compose uses service names automatically.
• Custom DNS via --dns 8.8.8.8 or daemon-wide.

Visual explanation

Architecture or command flow to keep in mind:

# inside the api container, after attaching to user-defined net
$ getent hosts db
172.18.0.2  db
$ curl http://web/

Step-by-step explanation

1. Run the command or manifest exactly once on a clean Docker host and read the output carefully.
2. Inspect the object Docker created: image, container, network, volume, port mapping, process, or registry tag.
3. Break one realistic assumption such as a missing port, bad tag, stopped daemon, wrong network, or deleted volume.
4. Use docker ps, logs, inspect, stats, and system df to locate the failure.
5. Write the final command or configuration into a repeatable script, Compose file, or CI job.

Informative example

Use the example below as a working baseline, then verify the runtime behavior instead of assuming the command or file is correct.

# inside the api container, after attaching to user-defined net
$ getent hosts db
172.18.0.2  db
$ curl http://web/

A production-minded check usually includes docker ps, docker logs, docker inspect, and one validation from outside the container such as curl, a database connection, or a registry pull.

# Verification loop for Container DNS & Discovery
docker ps -a
docker logs --tail=100 <container-name>
docker inspect <container-or-image-name>
docker system df

Real-world use

DNS-based discovery is what makes microservices in Docker (and Kubernetes) pleasant — no config of IPs, just talk to a logical name.

Enterprise use cases

In a mature engineering organization, Container DNS & Discovery is documented as a repeatable pattern with approved base images, ownership labels, CI checks, security expectations, rollback notes, and troubleshooting commands. The difference between a tutorial and production practice is that every container decision must be observable, reviewable, and reversible.

Best practices

• Pick clear, short service names (api, db, queue).
• Avoid hardcoded IPs in app config.

Common mistakes

• Relying on the default bridge — no DNS there.

Debugging tips

• Start with docker ps and docker port to confirm whether the container is running and the expected host port is published.
• Inspect the network with docker network inspect and test DNS from another container on the same user-defined network.
• Remember that EXPOSE documents intent; -p or Compose ports publishes traffic to the host.

Optimization strategies

• Prefer explicit names, labels, tags, and networks so cleanup and debugging stay predictable.
• Pin versions for repeatability, then update intentionally through a scheduled base-image refresh.
• Use docker system df and targeted prune commands to control local and CI disk growth.

Advanced interview questions

Hands-on exercise

Create a small lab for Container DNS & Discovery: run the example, inspect the created Docker object, intentionally introduce one mistake, and record the command that reveals the failure. The goal is not just to make the happy path work; it is to build operational reflexes.

# Hands-on lab scaffold
mkdir -p docker-container-dns-discovery-lab
cd docker-container-dns-discovery-lab

# Add the Dockerfile, compose.yml, or command from this lesson.
# Then run one happy-path test and one broken-path test.
docker version
docker info
docker system df

Summary

Container DNS & Discovery matters because Docker is not only a packaging tool; it is a runtime, build, networking, storage, and delivery workflow. Treat each lesson as a production habit: make it repeatable, inspectable, secure, and easy to debug.