Error message no valid A records found, even if there are already A records

When using the self-built dns authorization server to resolve the domain name, the application certificate will return no valid A records found, it seems that it only happens in let's encrypt, when the certificate server uses ZeroSSL, the certificate can be applied normally。

My domain is:

I ran this command: --issue -d --standalone

My web server is (include version): acme standalone server

The operating system my web server runs on is (include version): CentOS Stream release 9

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): no

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): GitHub - acmesh-official/ A pure Unix shell script implementing ACME client protocol v3.0.6

It produced this output:
[root@trojan ~]# --issue -d --standalone

[2023年 02月 04日 星期六 18:12:20 CST] Using CA:

[2023年 02月 04日 星期六 18:12:20 CST] Standalone mode.

[2023年 02月 04日 星期六 18:12:20 CST] Single domain=''

[2023年 02月 04日 星期六 18:12:20 CST] Getting domain auth token for each domain

[2023年 02月 04日 星期六 18:12:23 CST] Getting webroot for domain=''

[2023年 02月 04日 星期六 18:12:23 CST] Verifying:

[2023年 02月 04日 星期六 18:12:23 CST] Standalone mode server

[2023年 02月 04日 星期六 18:12:24 CST] Pending, The CA is processing your order, please just wait. (1/30)

[2023年 02月 04日 星期六 18:12:28 CST] error:no valid A records found for; no valid AAAA records found for

[2023年 02月 04日 星期六 18:12:28 CST] Please add '--debug' or '--log' to check more details.

[2023年 02月 04日 星期六 18:12:28 CST] See: How to debug · acmesh-official/ Wiki · GitHub

[2023年 02月 04日 星期六 18:12:29 CST] Please refer to libcurl - Error Codes for error code: 22

It looks like your DNS server has a lot of issues that need to be fixed in order for your domain name to properly work:

There's lame delegation in there, and the servers that are supposed to be authoritative aren't saying they are. You first need to have your site working before you try to get a certificate through HTTP-01.


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