Perplexing error report from Cpanel

[jeffschips]

Received the following message this a.m. and am totally perplexed what does it mean?

Cron <[email protected]> /usr/local/cpanel/bin/autossl_check --all

[1611567636] libunbound[7672:0] info: response for l.root-servers.net. AAAA IN
[1611567636] libunbound[7672:0] info: reply from <net.> 2001:502:1ca1::30#53
[1611567636] libunbound[7672:0] info: query response was REFERRAL


What does this mean?

 

[cPRex]

Hey there! Are there any other logs around that same point in time? Usually this indicates a failure of the AutoSSL system to renew a certificate, so there are likely DNS problems on your machine. You would likely be able to recreate this issue using the details outlined in this article:

How to diagnose AutoSSL issues using /scripts/cpdig

When AutoSSL runs, it performs a few checks that need to pass before a certificate can be issued successfully. Many times these failures can be attributed to DNS checks not validating or returnin...

support.cpanel.net

so can you try that and see if that gets you more information?

 

[jeffschips]

Hi Jurassic - your suggestion worked. Now I see the following which I presume is correct for such an action? I've replaced my tld domain with "tld".


[[email protected] scripts]# ./cpdig tld.com A --verbose
[1611603783] libunbound[9513:0] notice: init module 0: validator
[1611603783] libunbound[9513:0] notice: init module 1: iterator
[1611603783] libunbound[9513:0] info: resolving tld.com. A IN
[1611603783] libunbound[9513:0] info: priming . IN NS
[1611603783] libunbound[9513:0] info: response for . NS IN
[1611603783] libunbound[9513:0] info: reply from <.> 192.33.4.12#53
[1611603783] libunbound[9513:0] info: query response was ANSWER
[1611603783] libunbound[9513:0] info: response for . NS IN
[1611603783] libunbound[9513:0] info: reply from <.> 199.7.83.42#53
[1611603783] libunbound[9513:0] info: query response was ANSWER
[1611603783] libunbound[9513:0] info: priming successful for . NS IN
[1611603783] libunbound[9513:0] info: response for tld.com. A IN
[1611603783] libunbound[9513:0] info: reply from <.> 192.203.230.10#53
[1611603783] libunbound[9513:0] info: query response was REFERRAL
[1611603783] libunbound[9513:0] info: response for tld.com. A IN
[1611603783] libunbound[9513:0] info: reply from <com.> 192.33.14.30#53
[1611603783] libunbound[9513:0] info: query response was REFERRAL
[1611603783] libunbound[9513:0] info: resolving ns2.tld.com. AAAA IN
[1611603783] libunbound[9513:0] info: resolving ns1.tld.com. AAAA IN
[1611603783] libunbound[9513:0] info: response for tld.com. A IN
[1611603783] libunbound[9513:0] info: reply from <tld.com.> 55.xx.xxx.xxx#53
[1611603783] libunbound[9513:0] info: query response was ANSWER
[1611603783] libunbound[9513:0] info: response for ns2.tld.com. AAAA IN
[1611603783] libunbound[9513:0] info: reply from <tld.com.> 55.xx.xxx.xxx#53
[1611603783] libunbound[9513:0] info: query response was ANSWER
[1611603783] libunbound[9513:0] info: response for ns1.tld.com. AAAA IN
[1611603783] libunbound[9513:0] info: reply from <tld.com.> 55.xx.xxx.xxx#53
[1611603783] libunbound[9513:0] info: query response was ANSWER

 

[jeffschips]

I'm wondering what would have accounted for the hiccup previously?

 

[cPRex]

Most likely? Temporary network issues, either on your end, the host, or the SSL provider, or something in between all of those locations. It's not really possible to narrow it down to anything more specific than that, unfortunately.

That output looks pretty standard to me now, and as long as your not getting any errors from the main /usr/local/cpanel/bin/autossl_check command things are good!