[GH-ISSUE #550] [Bug] dynv6获取证书报错 #358

Closed
opened 2026-03-03 01:02:43 +03:00 by kerem · 3 comments
Owner

Originally created by @liruya on GitHub (Mar 23, 2025).
Original GitHub issue: https://github.com/certimate-go/certimate/issues/550

看到已经更新了获取dynv6证书, 但在执行流程时报错:
error: one or more domains had a problem: [ifoolu.dynv6.net] [ifoolu.dynv6.net] acme: error presenting token: dynv6: [fqdn=_acme-challenge.ifoolu.dynv6.net.] unexpected response for '_acme-challenge.ifoolu.dynv6.net.' [question='_acme-challenge.ifoolu.dynv6.net. IN SOA', code=SERVFAIL]
这是什么情况

环境
群晖 docker

Originally created by @liruya on GitHub (Mar 23, 2025). Original GitHub issue: https://github.com/certimate-go/certimate/issues/550 看到已经更新了获取dynv6证书, 但在执行流程时报错: error: one or more domains had a problem: [ifoolu.dynv6.net] [ifoolu.dynv6.net] acme: error presenting token: dynv6: [fqdn=_acme-challenge.ifoolu.dynv6.net.] unexpected response for '_acme-challenge.ifoolu.dynv6.net.' [question='_acme-challenge.ifoolu.dynv6.net. IN SOA', code=SERVFAIL] 这是什么情况 **环境** 群晖 docker
kerem 2026-03-03 01:02:43 +03:00
  • closed this issue
  • added the
    bug
    stale
    labels
Author
Owner

@fudiwei commented on GitHub (Mar 23, 2025):

docker logs 看一下 ACME 日志信息还有其他内容吗?

<!-- gh-comment-id:2746280918 --> @fudiwei commented on GitHub (Mar 23, 2025): docker logs 看一下 ACME 日志信息还有其他内容吗?
Author
Owner

@fudiwei commented on GitHub (Mar 23, 2025):

Image

我这是正常的 😕 可以给你几个排查思路:

  1. certimate 申请配置的 DNS 递归服务器填个 8.8.8.8
  2. 确认一下运行 certimate 的 docker 容器是否开启了 ipv6 支持:https://docs.docker.com/config/daemon/ipv6/
  3. 在 dynv6 里添加个 ipv4 的解析(随便解析到哪儿都行),不要只用纯 ipv6。
<!-- gh-comment-id:2746287508 --> @fudiwei commented on GitHub (Mar 23, 2025): > ![Image](https://github.com/user-attachments/assets/4f0a8d17-9792-46c9-bff4-e569fe6cfb1c) 我这是正常的 😕 可以给你几个排查思路: 1. certimate 申请配置的 DNS 递归服务器填个 `8.8.8.8`。 2. 确认一下运行 certimate 的 docker 容器是否开启了 ipv6 支持:https://docs.docker.com/config/daemon/ipv6/ 3. 在 dynv6 里添加个 ipv4 的解析(随便解析到哪儿都行),不要只用纯 ipv6。
Author
Owner

@fudiwei commented on GitHub (Apr 22, 2025):

This issue is stale because it has been open for 30 days with no activity.

<!-- gh-comment-id:2821066324 --> @fudiwei commented on GitHub (Apr 22, 2025): This issue is stale because it has been open for 30 days with no activity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/certimate#358
No description provided.