My DNS takes 24 hours to update the txt files

[Percy]

My domain is: spiritual-essences.com

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is: Heart Internet

I can login to a root shell on my machine - YES

I have loaded up 6 cet txt files, over a 48 hour period, but my ISP take a least 24 hours minimum to update the txt files in the DNS zone. I am unable to keep the ‘letsencrypt’ script paused for so a long time, and so I have to run the script agaain, but as the ‘letsencrpt’ creates a new code’ each time it runs… I am never going to be able to satisfy the requirments.

Is there another way that we can ‘ping’ to check that the TXT files are valid in my dns txt files ? because when i run the script again… it ignores the old ‘letsencrypt’ txt files…

How you other another way please

Best wishes

[JuergenAuer]

Hi @Percy

@Percy

I have loaded up 6 cet txt files, over a 48 hour period, but my ISP take a least 24 hours minimum to update the txt files in the DNS zone. I am unable to keep the ‘letsencrypt’ script paused for so a long time, and so I have to run the script agaain, but as the ‘letsencrpt’ creates a new code’ each time it runs… I am never going to be able to satisfy the requirments.

Is there another way that we can ‘ping’ to check that the TXT files are valid in my dns txt files ? because when i run the script again… it ignores the old ‘letsencrypt’ txt files…

if your ISP is so slow, you should change.

But checking your domain, the wrong entries are created - https://check-your-website.server-daten.de/?q=spiritual-essences.com#txt

The first four entries are completely wrong.

Compare it with

The Domain name must start with _acme-challenge. And the TXT entry: There is no _acme-challenge.yourdomainname allowed.

[Percy]

Hi, Thank you… I understand now, I will correct

Thank you

Best wishes

[jvanasco]

@JuergenAuer

if your ISP is so slow, you should change.

Most DNS providers have issues that can affect LetsEncrypt validation. While I do not think 24hours is acceptable, a lot of similar issues can happen with shorter times. IMHO, changing a hosting provider will not necessarily fix an issue lie this.

It looks like the hosting provider is a subsidiary of a subsidiary of a subsidiary of a subsidiary of godaddy. There are a lot of customer support options to improve that DNS time.

However, if the OP is technically inclined, running acme-dns (GitHub - joohoi/acme-dns: Limited DNS server with RESTful HTTP API to handle ACME DNS challenges easily and securely.) on a server is the best way to handle DNS challenges.