• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

"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