• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

setting nameservers for my new server

A

ashley1

Guest
Hi , guys is there any tutorial that will help me set up nameservers ns1.myhost.com and ns2.myhost.com for my new server so that i point my domain names to them .
i did lot of reseach but nothing helps,
thank you,
 
Nameserver problems

I have not been able to figure out what the proper settings for the nameservers on my Plesk box.

I would like to be able to have my hosted clients point their domains' DNS entries to NS1.mydomain.com and NS2.mydomain.com, but I tried pointing one of my other domains to these nameservers and even when it propagated it did nothing.

This is how I have it set up:

<domain>. A XX.XX.XX.01
<domain>. MX (10) mail.<domain>.
<ip> / 24 PTR <domain>.
ftp.<domain>. CNAME <domain>.
mail.<domain>. A <ip>
ns.<domain>. A <ip>
ns1.<domain>. A XX.XX.XX.01
ns2.<domain>. A XX.XX.XX.02
webmail.<domain>. A <ip>


(I have changed the IP addresses to X's just for the purposes of this post)
I have done a reverse DNS lookup and the IP's both check out.

Note:
ftp works for my main domain.
mail.mydomain.com gives a 404
webmail.mydomain.com gives a 404
I am able to send and receive mail from an account on my main domain.

Does anyone have any ideas? I need this to work.
 
Back
Top