Skip to main content

Domain failed domain control validation - domain does not resolve

Comments

4 comments

  • Hays Sleiman
    This issue is happening to all the domains on the server. But I've SSH'd in to the server and ran curl and ping on one of the domains. It seems to be okay, yet when i run AutoSSL on it, it still says doesn't resolve to an IP4 address on this server. I don't understand and this issue is starting to be a problem because all our customers' emails are being ignored by Outlook because of the bad SSL cert. Here are the results for the commands: [root@ms1 ~]# curl -v mail.domain.com.au * About to connect() to mail.domain.com.au port 80 (#0) * Trying X.X.X.207... * Connected to mail.domain.com.au (X.X.X.207) port 80 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.29.0 > Host: mail.domain.com.au > Accept: */* > < HTTP/1.1 200 OK < Date: Thu, 22 Mar 2018 10:53:29 GMT < Server: Apache < Content-Length: 623 < Content-Type: text/html;charset=ISO-8859-1 < Index of /

    Index of /

      Name Last modified Size Description

      cgi-bin/ 2018-03-20 14:40 -  

    * Connection #0 to host mail.domain.com.au left intact [root@ms1 ~]# ping mail.domain.com.au PING ms1.domain.com.au (X.X.X.207) 56(84) bytes of data. 64 bytes from ms1.domain.com.au (X.X.X.207): icmp_seq=1 ttl=64 time=0.035 ms 64 bytes from ms1.domain.com.au (X.X.X.207): icmp_seq=2 ttl=64 time=0.065 ms 64 bytes from ms1.domain.com.au (X.X.X.207): icmp_seq=3 ttl=64 time=0.038 ms 64 bytes from ms1.domain.com.au (X.X.X.207): icmp_seq=4 ttl=64 time=0.047 ms 64 bytes from ms1.domain.com.au (X.X.X.207): icmp_seq=5 ttl=64 time=0.045 ms ^C --- ms1.serverpoint.com.au ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3999ms rtt min/avg/max/mdev = 0.035/0.046/0.065/0.010 ms [root@ms1 ~]#

    Please any help would be appreciated. Thank you.
    0
  • Hays Sleiman
    I have opened a support ticket for this issue, but any tips in the meantime would be great.
    0
  • cPanelMichael
    Hello, It looks like we've responded to the support ticket. I'll continue to monitor the ticket and update this thread with the outcome once it's complete. Thanks!
    0
  • cPanelMichael
    Hello, To update, it looks like this was determined to relate to an internal case associated with AutoSSL and certain CNAME records. It's fixed in cPanel & WHM version 70: Fixed case CPANEL-17973: Fix recursive DNS resolver"s handling of CNAME records. Thank you.
    0

Please sign in to leave a comment.