• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

"Add subdomain" adds the subdomain, but incorrectly claims that the subdomain cannot be resolved

Bitpalast

Plesk addicted!
Plesk Guru
Username: Peter Debik

TITLE

"Add subdomain" adds the subdomain, but incorrectly claims that the subdomain cannot be resolved

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Obsidian, latest MU
CentOS 7.9

PROBLEM DESCRIPTION

"Add subdomain" creates the subdomain, but closes with an error message that claims that the subdomain cannot be resolved and that the user shall update his DNS settings.

However, the domain has a subdomain wildcard entry and resolves correctly to the server's IP address.

The Plesk DNS component is not installed on the server. All DNS entries are managed externally.

The server name resolution works, e.g. when I
# ping <subdomain>
I am seeing the correct IP address of that domain that is only resolved by a DNS wildcard entry on the external nameserver.

STEPS TO REPRODUCE

Click "Add subdomain" and add a subdomain.

ACTUAL RESULT

"Warnung: Die Domain kann nicht aufgelöst werden. Um Ihre Website online zu stellen, korrigieren Sie DNS-Einstellungen."
In English probably very similar to
"Warning: The domain cannot be resolved. To put your website online, correct the DNS settings."

EXPECTED RESULT

No DNS warning as the domain can be resolved.

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
having the same trouble even after removing the subdomain. we hav 4, count 'em, 4 orange warning boxes. clicking on the dns settings link drives us to a db error box with unrelated id's and the repair tool never accepts the plesk admin credentials. It's all pretty broken and there doesn't seem to be a knowledge base or actual solution to this problem.
 
Back
Top