• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question DNS Issues When Using Plesk as Primary Server

Medina

New Pleskian
Server operating system version
Debian 9.13
Plesk version and microupdate number
Plesk Obsidian Web Host Edition 18.0.44
Hello,

I am experiencing difficulties with DNS and am unsure whether they are due to configuration errors or specific behavior in Plesk.

I am using Plesk as the primary DNS server, and when I create a domain, the system automatically generates all the necessary records. However, after the domain is created, I receive the following message:

"The domain does not resolve, the domain name is not recognized, or it corresponds to a different IP address. To publish the website, update the DNS settings with your domain registrar or external DNS provider. Your site will be ready once the DNS changes take effect, which may take up to 24 hours."

All DNS records were created automatically by Plesk, but the domain is still not recognized. Could you clarify whether this issue is related to Plesk or if additional configuration is required on the registrar’s side?

Thank you!
 

Attachments

  • Снимокddddddddddddddddddddddddddddddddddddddddddddd.PNG
    Снимокddddddddddddddddddddddddddddddddddddddddddddd.PNG
    3.6 KB · Views: 1
Back
Top