• 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.

Resolved Subdomains no longer working!!!

jayplesk2015

Basic Pleskian
Server operating system version
CentOS Linux
Plesk version and microupdate number
Obsidian
Hey Everyone

I have been using the Plesk platforms for YEARS< did they alter something. We used to seup a hundred test subdomains back in the day, and BAM! we were immediately installing (first Joomla, then Wordpress) systems onto them,

Now in Obsidian whenever we create a subdomain we get immediate "cannot resolve" errors, even though the TLD is perfectly fine.

Did they create a new version of Plesk so when it installs a subdomain , we now have to do something different

VERY frustrating, hopefully someone can help, this behavior NEVER took place in Cpanel, and it also never used to happen in Plesk!

Thanks for ANY help!
 

Attachments

  • dnsissue1.jpg
    dnsissue1.jpg
    69.5 KB · Views: 19
  • dnsissue2.jpg
    dnsissue2.jpg
    212.1 KB · Views: 18
Because you are not using the DNS service with your server you will need to log into your registrar and create the A records accordingly. Alternatively you can update your name servers in your registrar to point to your server (which usually sometimes requires you to create a glue record. You'll need to refer to your registrar for details about that).
 
Because you are not using the DNS service with your server you will need to log into your registrar and create the A records accordingly. Alternatively you can update your name servers in your registrar to point to your server (which usually sometimes requires you to create a glue record. You'll need to refer to your registrar for details about that).
Hey man!

I already have the records for he TLD in there, are you saying I need to create a NEW set for the subdomain as well?
 

Attachments

  • 2023-04-13_17-46-17.jpg
    2023-04-13_17-46-17.jpg
    219.2 KB · Views: 17
You would just need to add an A record for just the subdomain (in this case, it would be your test.whynotgus.info).

So add a new record type of A, host being test.whynotgus.info, answer will be your 207.244.253.135, ttl can be left at default, and that's it.
 
Another option would be to always create a wildcard * A-record so that for additional subdomains you won't have to create them individually.
 
Back
Top