Skip to main content

accessing WHM is not secure any more

Comments

7 comments

  • cPRex Jurassic Moderator

    Hey there!  If you scan your domain with a tool like intodns.com, do you see any errors for your domain.com?  If there are *any* DNS errors AutoSSL will not be able to issue the certificate.

    0
  • greektranslator

    I get Same Glue error. The parent is different from nameservers it says. But I have made no changes whatsoever and it had been working fine so far.

    0
  • cPRex Jurassic Moderator

    It doesn't matter if you haven't made any changes - *something* in the DNS for the domain has changed, possibly at the registrar level.  Can you look into that a bit more?

    0
  • greektranslator

    Thanks, at registrar-level there are only 2 entries for ns1... and ns2... for the main domain (the one used to log in to WHM via host.[domain.name])

    0
  • cPRex Jurassic Moderator

    That sounds right, but the lack of glue record could indicate the nameservers aren't properly configured where they are registered.

    0
  • greektranslator

    Reply from registrar:

    The Nameservers are correctly registered in the Domain Name Registry. The issue seems to arise due to a Glue mismatch between the Registry and the A records on your DNS servers, resulting in the latter returning only the IP: 176.31.xxx.xxx, which you can also confirm here: https://network-tools .webwiz.net/dns-report.htm . In addition, if you think that the DNS records have been correctly passed to your Server, please check if there is any relevant record in the Hosts.

    I checked the A record in DNS Zone Manager and changed the ns2 IP so it is the same as ns1 IP. Is this what I should do? The same issue persists.

    0
  • cPRex Jurassic Moderator

    Yes, it sounds like that is what you should do, but it may take a few hours for DNS propagation to update before any online tools will see the change.

    0

Please sign in to leave a comment.