Article ID: 119332, created on Dec 26, 2013, last review on Oct 9, 2016

  • Applies to:
  • Plesk 12.0 for Linux
  • Plesk 11.0 for Linux
  • Plesk 11.5 for Linux
  • Plesk 12.5 for Windows
  • Plesk 12.0 for Windows
  • Plesk 11.0 for Windows
  • Plesk 11.5 for Windows


A domain is not resolving to the server correctly.


Issue with configuration or availability of DNS server.


  1. Make sure that the domain is correctly registered on the domain registrar side and that the A type DNS records point to the correct server. Kindly note that adding of DNS records will take up to 24 hours to propagate. In order to check it use dig or nslookup utility.

  2. Make sure that the DNS zone is active for the domain in Plesk under Domains > > DNS settings.

  3. Make sure that DNS service is running in Plesk at Tools & Settings > Services Management.

  4. Check that DNS zone for the domain is correct and persists in Plesk database. Use the following command:

    plesk db "SELECT,,, dns_zone.displayName FROM domains LEFT JOIN dns_zone ON (domains.dns_zone_id = WHERE'';"

    In addition, a domain should have only one DNS zone and if more than one DNS zones displays, please contact Plesk technical support.

    Note: Use for the reference: #3472 - How to access Plesk database?.

  5. Update the domain's DNS settings:

    • For Windows:

      "%plesk_bin%\DNSMng.exe" update
    • For Linux:

      /usr/local/psa/admin/bin/dnsmng --update

Search Words

website not display for website

DNS issues


Dns not resolving

Name servers not working

DNS zone

default ssl propigates

Plesk domain not working

RSA server certificate CommonName (CN) `Parallels Panel' does NOT match server name!?

dns plesk

Domain name not resolve issue may due to `Parallels Panel' does NOT match server name

dns queries

a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 514af229ae32522202a910a2649c80fb 85a92ca67f2200d36506862eaa6ed6b8 bd7fc88cf1b01f097749ae6f87272128 46a8e394d6fa13134808921036a34da8 29d1e90fd304f01e6420fbe60f66f838 aea4cd7bfd353ad7a1341a257ad4724a 0a53c5a9ca65a74d37ef5c5eaeb55d7f ed7be2b984f9c27de1d2dc349dc19c6d a766cea0c28e23e978fa78ef81918ab8 2a5151f57629129e26ff206d171fbb5f e335d9adf7edffca6a8af8039031a4c7 8b661cab116c79dbe6c4ac5bbdf1c8cb 01bc4c8cf5b7f01f815a7ada004154a2

Email subscription for changes to this article
Save as PDF