Skip to main content

AutoSSL "domain.tld" is unmanaged

Comments

7 comments

  • cPRex Jurassic Moderator
    Hey there! *Something* must be up with the DNS in order for the tool to generate that error. Can you try scanning the domain with intodns.com and see if there is anything out of the ordinary listed there?
    0
  • Ryanb977
    Everything is either green or blue. The only this is there is a warning for "Not all of your nameservers are in different subnets" but thats because I just have one server for everything.
    0
  • cPRex Jurassic Moderator
    Alright, so the resolver test is good and DNS itself looks good. Can you try this command to see if it shows anything useful? /scripts/cpdig domain.com A --verbose
    Just replace "domain.com" with the domain you're checking and see if that shows anything helpful.
    0
  • Ryanb977
    So I got this as a result. 0.0.0.0 is my domain's IP. [1695792629] libunbound[1279029:0] notice: init module 0: validator [1695792629] libunbound[1279029:0] notice: init module 1: iterator [1695792629] libunbound[1279029:0] info: resolving domain.tld. A IN [1695792629] libunbound[1279029:0] info: priming . IN NS [1695792629] libunbound[1279029:0] info: response for . NS IN [1695792629] libunbound[1279029:0] info: reply from <.> 199.9.14.201#53 [1695792629] libunbound[1279029:0] info: query response was ANSWER [1695792629] libunbound[1279029:0] info: priming successful for . NS IN [1695792629] libunbound[1279029:0] info: resolving l.root-servers.net. AAAA IN [1695792629] libunbound[1279029:0] info: resolving m.root-servers.net. AAAA IN [1695792629] libunbound[1279029:0] info: resolving m.root-servers.net. A IN [1695792629] libunbound[1279029:0] info: response for l.root-servers.net. AAAA IN [1695792629] libunbound[1279029:0] info: reply from <.> 192.203.230.10#53 [1695792629] libunbound[1279029:0] info: query response was REFERRAL [1695792629] libunbound[1279029:0] info: response for m.root-servers.net. AAAA IN [1695792629] libunbound[1279029:0] info: reply from <.> 198.97.190.53#53 [1695792629] libunbound[1279029:0] info: query response was REFERRAL [1695792629] libunbound[1279029:0] info: response for m.root-servers.net. A IN [1695792629] libunbound[1279029:0] info: reply from <.> 192.58.128.30#53 [1695792629] libunbound[1279029:0] info: query response was REFERRAL [1695792629] libunbound[1279029:0] info: response for domain.tld. A IN [1695792629] libunbound[1279029:0] info: reply from <.> 193.0.14.129#53 [1695792629] libunbound[1279029:0] info: query response was REFERRAL [1695792629] libunbound[1279029:0] info: response for domain.tld. A IN [1695792629] libunbound[1279029:0] info: reply from 192.33.14.30#53 [1695792629] libunbound[1279029:0] info: query response was REFERRAL [1695792629] libunbound[1279029:0] info: resolving ns2.domain.tld. AAAA IN [1695792629] libunbound[1279029:0] info: resolving ns1.domain.tld. AAAA IN [1695792629] libunbound[1279029:0] info: response for domain.tld. A IN [1695792629] libunbound[1279029:0] info: reply from 0.0.0.0#53 [1695792629] libunbound[1279029:0] info: query response was ANSWER 0.0.0.0
    0
  • cPRex Jurassic Moderator
    That looks perfect to me - I've run out of obvious things to check on my end, so could you submit a support ticket to our team and then post the number here so I can follow along?
    0
  • Ryanb977
    The Ticket ID is 95130287
    0
  • cPRex Jurassic Moderator
    Thanks for that - it looks like our team found potential DNS propagation problems with the zone as it doesn't seem to be properly resolving at all times. If you don't believe the issue is related to propagation, and the DNS has not been changed for 48 hours or more, please let us know in the ticket so we can try some additional tests.
    0

Please sign in to leave a comment.