Docker 29.1.0 - DNS issues

Hello,

After upgrading to 29.1.0, containers no longer use the DNS settings from the host. I see this on multiple hosts.
I have to manually add per container:
service:
app:
dns:
- 1.1.1.1
- 1.0.0.1
Even setting the global DNS settings in daemon.json have no effect.

# docker version
Client: Docker Engine - Community
 Version:           29.1.0
 API version:       1.52
 Go version:        go1.25.4
 Git commit:        360952c
 Built:             Thu Nov 27 16:42:29 2025
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
  Version:          29.1.0
  API version:      1.52 (minimum version 1.44)
  Go version:       go1.25.4
  Git commit:       710302e
  Built:            Thu Nov 27 16:42:29 2025
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v2.1.5
  GitCommit:        fcd43222d6b07379a4be9786bda52438f0dd16a1
 runc:
  Version:          1.3.3
  GitCommit:        v1.3.3-0-gd842d771
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
# cat /etc/docker/daemon.json
{
  "default-address-pools": [
    {
      "base": "172.16.0.0/12",
      "size": 24
    }
  ],
  "dns": ["1.1.1.1", "1.0.0.1"],
  "log-driver": "syslog",
  "log-opts": {
    "tag": "{{.Name}}"
  }
}

Please advice, thanks!

It seems there was a DNS issue indeed and a change was reverted and released as 29.1.1. Try upgrading and see if that fixes the issue.

Link to the release notes:

https://docs.docker.com/engine/release-notes/29/#2911

1 Like

Yep, upgrading to 29.1.1 fixed the issue. Thanks.

That’s great. Then please consider marking my post as solution by clicking on the gray "checkbox icon under the post, so it will be more obvious that the topic was solved.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.