• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Resolved Sub domain not yet propagated

mmsaaa

New Pleskian
It's now over 12 hours but my subdomain still not propagated, if it will take more time, I remember subdomain used to work instantly in other platforms, in Plesk Obsidian why it not pointing instantly. Is there anything else I can do. I simply created subdomain and I can see A level entry created in the main DNS toward IP address. I m using digital ocean name servers for the main domain.
 
It's now over 12 hours but my subdomain still not propagated, if it will take more time, I remember subdomain used to work instantly in other platforms, in Plesk Obsidian why it not pointing instantly. Is there anything else I can do. I simply created subdomain and I can see A level entry created in the main DNS toward IP address. I m using digital ocean name servers for the main domain.
What dns you are using and what is your TTL?
 
I have just restored my main domain site so what happens in Plesk, my subdomain DNS entries were missing after restoration, so I added A entry of this subdomain with IP number. Even before restoration, it was there.

Because subdomain DNS entry is setup in main domain so after restoration from an old back up its gone missing.

Now after 15-20 minutes I am able to access the site.

Don't know what happens last night, but it's working now after restoration and adding entry manually in DNS.


Will try making another subdomain and will see how it goes, will update here. Thank you @sebgonzes
 
Back
Top