Article ID: 127419, created on Nov 13, 2015, last review on Nov 13, 2015

  • Applies to:
  • Plesk Automation

Symptoms

Domain example.com cannot be resolved. The DNS zone is configured correctly in Plesk Automation, the query as below returns correct IP:

# dig +short example.com @ns1.isp.tld
172.16.0.11

# dig +short example.com @ns2.isp.tld
172.16.0.11

where ns1.isp.tld and ns2.isp.tld are Plesk Automation DNS service nodes.

Cause

The domain for some reason was put on hold on registrar side.

Resolution

  1. Run the following command in order to check domain status:

    # whois example.com |grep -i 'Domain Status'
    Domain Status: clientHold
    Domain Status: clientTransferProhibited
    Domain Status: clientUpdateProhibited
    

    the status clientHold indicates that the domain was suspended on registrar side. You can find more details at ICANN EPP status codes page

  2. Contact domain registrar in order to clarify the reason why the domain was suspended. The registrar contact can be found in full whois output:

    # whois example.com
    

Search Words

Domain is not resolving

domain

domain is not working

domain does not ressolve

e0aff7830fa22f92062ee4db78133079 caea8340e2d186a540518d08602aa065

Email subscription for changes to this article
Save as PDF