• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

No A records exist for my-domain.com.

W

WebhostPeter

Guest
I am at a loss
server-hosts.com (the nameservers are ns1.server-hosts.com and ns2.server-hosts.com) can't be found. The sites on the server work normally (most of them) except the ones with a registration in the Netherlands, if I look here
http://www.dnsstuff.com/tools/lookup.ch?name=server-hosts.com&type=A
it tells me there is no A record, however if I look here
72.232.37.242 / 24 PTR server-hosts.com.
ftp.server-hosts.com. CNAME server-hosts.com.
mail.server-hosts.com. A 72.232.37.242
ns1.server-hosts.com. A 72.232.37.242
ns2.server-hosts.com. A 72.232.40.111
server-hosts.com. NS ns2.server-hosts.com.
server-hosts.com. NS ns1.server-hosts.com.
server-hosts.com. MX (10) mail.server-hosts.com.
server-hosts.com. TXT v=spf1 a mx ~all
webmail.server-hosts.com. A 72.232.37.242
www.server-hosts.com. CNAME server-hosts.com.
There are a few A records. Can ANYONE tell me what to do? My registrar isn't very helpful, plesk support neither, and all other resources can't help me either.

Additionally this problem occurred suddenly, before it worked fine.
 
Plesk support just fixed the problem (after almost 5 days)
 
Back
Top