ubuntu/bind9Current Bind9 Docker Image from Canonical, based on Ubuntu. Receives security updates and tracks the newest combination of Bind9 and Ubuntu. This repository is free to use and exempted from per-user rate limits.
BIND 9 provides software for Domain Name System (DNS) management including both defining domain names authoritatively for a given DNS zone, and recursively resolving domain names to their IP addresses. In addition to BIND 9's DNS server itself, named, this container also includes tools for performing DNS queries and dynamic updates. Read more on the BIND 9 website.
!LTS Up to 5 years free security maintenance on LTS channels.
!ESM
Up to 10 years customer security maintenance from canonical/bind9. Request access.
Tags in italics are not available in ubuntu/bind9 but are shown here for completeness.
| Channel Tag | Currently | Architectures | ||
|---|---|---|---|---|
9.18-22.04_beta | !LTS | Bind9 9.18 on Ubuntu 22.04 LTS | amd64, arm64, ppc64el, s390x | |
9.16-20.04_beta | !LTS | Bind9 9.16.1 on Ubuntu 20.04 LTS | amd64, arm64, ppc64el, s390x | |
track_risk |
Channel Tag shows the most stable channel for that track. A track is a combination of both the application version and the underlying Ubuntu series, eg 1.0-22.04.
Channels are ordered from the most stable to the least stable, candidate, beta, edge.
More risky channels are always implicitly available.
So if beta is listed, you can also pull edge. If candidate is listed, you can pull beta and edge.
When stable is listed, all four are available.
Images are guaranteed to progress through the sequence edge, beta, candidate before stable.
If your usage includes commercial redistribution or requires unavailable channels/versions, please get in touch with the Canonical team (or using ***).
Launch this image locally:
shdocker run -d --name bind9-container -e TZ=UTC -p 30053:53 -p 30053:53/udp ubuntu/bind9:9.18-22.04_beta
Access your Bind9 server at localhost:30053
| Parameter | Description |
|---|---|
-e TZ=UTC | Timezone. |
-p 30053:53 | Expose bind9 on localhost:30053. |
-e BIND9_USER=bind | The user which will start the named process. |
-v /path/to/bind/configuration:/etc/bind/named.conf | Local configuration file named.conf (try this example). |
-v /path/to/cached/data:/var/cache/bind | Location where locally cached data can be dumped. |
-v /path/to/resource/records:/var/lib/bind | Location of Resource Records defining various domain information. |
To debug the container:
shdocker logs -f bind9-container
To get an interactive shell:
shdocker exec -it bind9-container /bin/bash
Works with any Kubernetes; if you don't have one, we recommend you install MicroK8s and microk8s.enable dns storage then snap alias microk8s.kubectl kubectl.
Download
bind9-deployment.yml and set containers.bind9.image in bind9-deployment.yml to your chosen channel tag (e.g. ubuntu/bind9:9.18-22.04_beta), then:
shkubectl apply -f bind9-deployment.yml
You will now be able to connect to the Bind9 server on localhost:30053`.
If you find a bug in our image or want to request a specific feature, please file a bug here:
[***]
Please title the bug "bind9: <issue summary>". Make sure to include the digest of the image you are using, from:
shdocker images --no-trunc --quiet ubuntu/bind9:<tag>
These channels (tags) are not updated anymore. Please upgrade to newer channels, or reach out if you can't upgrade.
| Track | Version | EOL | Upgrade Path |
|---|---|---|---|
| Bind9 9.16.15 on Ubuntu 21.10 | 07/2022 | 9.18-22.04_beta | |
track |
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务