• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

"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