主页 / unix / 问题 / 784930
Accepted
jamshid
Asked: 2024-10-12 01:05:33 +0800 CST

为什么 rockylinux 9 上的“dig”无法在 docker compose 网络中找到名为“https”的容器/主机？

  • 772

抱歉，我不知道这是 docker 问题还是 rockylinux 9 上的 dig 问题。在 rockylinux 8 上一切都按预期运行。

我有一个docker-compose.yml名为的文件，其中包含一个名为 的服务https。这允许通过主机名 引用容器https。虽然ping https可以工作，但由于某种原因dig https（DiG 9.16.23-RH）在 rockylinux 9 上不起作用。它在 rockylinux 8 上可以工作（DiG 9.11.36-RedHat-9.11.36-16.el8_10.2）。如果我将服务名称更改为httpsx然后dig httpsx就可以工作。

services:
  https:
    image: "rockylinux:${RL_VERSION}"
    command: bash -c "yum install -y iputils bind-utils && echo '=====dig version output====' && dig -v && echo '=====ping https output====' && ping -c 3 https && echo '=====dig https output====' && dig +short https"
    environment:
       - RL_VERSION

工作8：

% RL_VERSION=8 docker-compose up
Attaching to https-1
https-1  | Rocky Linux 8 - AppStream                       5.7 MB/s |  11 MB     00:01    
...
https-1  | Complete!
https-1  | =====dig version output====
https-1  | DiG 9.11.36-RedHat-9.11.36-16.el8_10.2
https-1  | =====ping https output====
https-1  | PING https (172.21.0.2) 56(84) bytes of data.
https-1  | 64 bytes from c3f0c7a6613c (172.21.0.2): icmp_seq=1 ttl=64 time=0.558 ms
https-1  | 64 bytes from c3f0c7a6613c (172.21.0.2): icmp_seq=2 ttl=64 time=0.051 ms
https-1  | 64 bytes from c3f0c7a6613c (172.21.0.2): icmp_seq=3 ttl=64 time=0.040 ms
https-1  | 
https-1  | --- https ping statistics ---
https-1  | 3 packets transmitted, 3 received, 0% packet loss, time 2025ms
https-1  | rtt min/avg/max/mdev = 0.040/0.216/0.558/0.241 ms
https-1  | =====dig https output====
https-1  | 172.21.0.2

失败9：

% RL_VERSION=9 docker-compose up
[+] Running 1/1
 ✔ Container testhttps-https-1  Recreated                                                                                                    0.2s 
Attaching to https-1
https-1  | Rocky Linux 9 - BaseOS                          2.4 MB/s | 2.4 MB     00:00    
...
https-1  | Complete!
https-1  | =====dig version output====
https-1  | DiG 9.16.23-RH
https-1  | =====ping https output====
https-1  | PING https (172.21.0.2) 56(84) bytes of data.
https-1  | 64 bytes from 4a2841b5dac9 (172.21.0.2): icmp_seq=1 ttl=64 time=0.404 ms
https-1  | 64 bytes from 4a2841b5dac9 (172.21.0.2): icmp_seq=2 ttl=64 time=0.117 ms
https-1  | 64 bytes from 4a2841b5dac9 (172.21.0.2): icmp_seq=3 ttl=64 time=0.088 ms
https-1  | 
https-1  | --- https ping statistics ---
https-1  | 3 packets transmitted, 3 received, 0% packet loss, time 2009ms
https-1  | rtt min/avg/max/mdev = 0.088/0.203/0.404/0.142 ms
https-1  | =====dig https output====
https-1  | c.root-servers.net.
https-1  | l.root-servers.net.
https-1  | e.root-servers.net.
https-1  | d.root-servers.net.
https-1  | i.root-servers.net.
https-1  | b.root-servers.net.
https-1  | g.root-servers.net.
https-1  | m.root-servers.net.
https-1  | a.root-servers.net.
https-1  | f.root-servers.net.
https-1  | h.root-servers.net.
https-1  | j.root-servers.net.
https-1  | k.root-servers.net.
docker

1 个回答

  1. Best Answer

    这既不是 Rocky 的问题，也不是 docker 的问题，而是一个dig怪癖；我在 Debian 12 上也看到了同样的问题。

    您所看到的是命令行解析的结果dig。通常语法（简单形式）可能被认为是，dig name [type]但它也接受。dig [type] name

    所以如果你做类似的事情，dig cname foobar它会寻找CNAMEfoobar 的资源记录 (RR)，就像你所做的一样dig foobar cname。

    如果不指定域，则输入整个查询将变为dig . ns

    现在https已经添加了 RR 类型，而在旧版本中它并不存在。

    这就是让您感到困惑的地方，因为在较新的版本中dig https看起来好像没有传递域名，因此会进行. ns查找。

    我们可以通过查看输出来看到这一点：

    % dig https

; <<>> DiG 9.16.23-RH <<>> https
;; global options: +cmd

...

;; QUESTION SECTION:
;.                              IN      NS

    答案是在查询前加上前缀-q。现在

    % dig -q https
...
;; QUESTION SECTION:
;https.                         IN      A
    • 2

相关问题