acme-client
acme-client copied to clipboard
kelunik
No response for 'domain.org' (MX) from any nameserver after 2 attempts
I am getting the following errors when running the setup command:
$ php bin/acme setup --server letsencrypt --email [email protected]
Amp\Dns\TimeoutException: No response for 'domain.org' (MX) from any nameserver after 2 attempts, tried udp://127.0.0.1:53, udp://153.92.2.25:53 in /home/.../acme-client/vendor/amphp/dns/lib/BasicResolver.php:299
Next Kelunik\Acme\AcmeException: Dns query for an MX record on 'domain.org' failed for the following reason: No response for 'domain.org' (MX) from any nameserver after 2 attempts, tried udp://127.0.0.1:53, udp://153.92.2.25:53 in /home/.../acme-client/src/Commands/Setup.php:83
I have SSH access to a server provided by Hostinger.
How to solve this?
It’s my company website: bloggify.org
Sent from my iPhone
On 26 Feb 2020, at 14:29, Niklas Keller [email protected] wrote:
Could you please share the real domain?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
bloggify.org itself is not hosted on Hostinger, but whatever email I use (even for domains hosted on my Hostinger account), I get the same error.
Could you share your
/etc/resolv.conf?
I'm running the script acme-client.phar on a shared hosting. Its /etc/resolv.conf has two nameserver entries aside from the following:
options timeout 1 attempts 3
These are the only three lines of code the file has.
@kelunik It has two nameservers entries too:
$ cat /etc/resolv.conf
# Ansible managed
nameserver 127.0.0.1
nameserver xxx.xx.x.xx
options timeout 1 attempts 3
I am pretty sure that Hostinger blacklisted the domains somehow. In any case, I installed the certificates via Cloudflare.
acme-client did work for a few months on Hostinger, but then they changed something I think.
I'll close this, as it seems to be a problem specific to Hostinger and not with the acme-client itself.