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

Problem with DNS Configuration

BrinsleyA

New Pleskian
I have a server and the server have two IPs NS1 point to XXX.XXX.XXX.XXX and NS2 point to YYY.YYY.YYY.YYY ( both point to SERVERDOMAIN.COM

If i create some costumer in plesk panel, and a domain on this costumer ( exemple: COSTUMERDOMAIN.COM ) and sets on registrar to NS1.SERVERDOMAIN.COM and NS2.SERVERDOMAIN.COM

Have these problems... In IntoDNS

IntoDNS:
Missing nameservers reported by parent: FAIL:
FAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1). You need to make sure that these nameservers are working.If they are not working ok, you may have problems!
NS1.COSTUMERDOMAIN.COM
NS2.COSTUMERDOMAIN.COM


Missing nameservers reported by your nameservers: ERROR:
One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
NS1.SERVERDOMAIN.COM
NS2.SERVERDOMAIN.COM
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).


My DNS Template is:

XXX.XXX.XXX.XXX / 24 PTR <domain>.
YYY.YYY.YYY.YYY / 24 PTR <domain>.
<domain>. NS ns1.<domain>.
<domain>. NS ns2.<domain>.
<domain>. A <ip.web>
<domain>. MX (0) mail.<domain>.
<domain>. TXT v=spf1 +a +mx ~all
ftp.<domain>. CNAME <domain>.
ipv4.<domain>. A <ip.web>
mail.<domain>. A <ip.mail>
ns1.<domain>. A XXX.XXX.XXX.XXX
ns2.<domain>. A YYY.YYY.YYY.YYY
webmail.<domain>. A <ip.webmail>



Why? How to fix this, i try some times fix but no have success...

Some can help?
 
Last edited:
Resolve the first problem by removing these from the template (and from the client's domain's actual DNS record in PLesk if removing them from the template doesn't do so automatically):

<domain>. NS ns1.<domain>.
<domain>. NS ns2.<domain>.

Next, remove these from the template:

ns1.<domain>. A XXX.XXX.XXX.XXX
ns2.<domain>. A YYY.YYY.YYY.YYY

Then add them *only* in the DNS record for serverdomain.com

Next, remove these from the template:
XXX.XXX.XXX.XXX / 24 PTR <domain>.
YYY.YYY.YYY.YYY / 24 PTR <domain>.

You should only have one PTR per IP address - put these records in the DNS for serverdomains.com for simplicity but there are other options. But normally those PTRs are never used so it doesn't matter much.

Errr....then try again and see what errors occur once you have done all that.

Also make absolutely sure you have created nameserver host records (sometimes called glue records) for serverdomain.com in serverdomain.com's registrars control panel.
 
Back
Top