Articles in this section

myLittleAdmin from a Plesk domain is unreachable at mssql.example.com: ERR_NAME_NOT_RESOLVED

Plesk for Windows kb: technical ABT: Group B

Applicable to:

  • Plesk for Windows

Symptoms

  • myLittleAdmin from a Plesk domain is unreachable at mssql.example.com. One of the following errors is shown in a browser:

    PLESK_INFO: ERR_NAME_NOT_RESOLVED


    PLESK_INFO: DNS_PROBE_FINISHED_NXDOMAIN

  • The MXToolBox DNS Lookup shows that a DNS record for mssql.example.com cannot be found. The same does the "nslookup" utility:

    C:\> nslookup mssql.example.com 8.8.8.8
    Server: google-public-dns-a.google.com
    Address: 8.8.8.8

    *** google-public-dns-a.google.com can't find mssql.example.com: Non-existent domain

  • The DNS zone example.com is hosted on an external DNS server.

Cause

There is no A-type DNS record for mssql.example.com on the external DNS server or said record has not been propagated yet.

Resolution

Note: If you are a domain owner, contact your service provider for assistance.

Add the A record for mssql.example.com on the external DNS server, which is responsible for the zone example.com.

If the A record exists, wait for DNS propagation. The propagation status for a domain can be checked at Global DNS Propagation Checker.

As a workaround, add '203.0.113.2 mssql.example.com' record in the hosts file on the workstation where Plesk Panel is opened:

  • Linux:

    /etc/hosts

  • Windows:

    %windir%\System32\drivers\etc\hosts

Was this article helpful?

Comments

0 comments

Please sign in to leave a comment.