• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • The ImunifyAV extension is now deprecated and no longer available for installation.
    Existing ImunifyAV installations will continue operating for three months, and after that will automatically be replaced with the new Imunify extension. We recommend that you manually replace any existing ImunifyAV installations with Imunify at your earliest convenience.

Resolved Local NS list does not match Parent NS list

Polli

Basic Pleskian
Server operating system version
Debian 12.9
Plesk version and microupdate number
18.0.67
I have my server running as primary DNS and my registrar as secondary DNS. This also works so far. However, there is still an error message.

Code:
Local NS list does not match Parent NS list
192.174.68.104 was reported locally, but not by the parent<br/>176.97.158.104 was reported locally, but not by the parent

Screenshot 2025-02-05 223033.png

How can I implement the corresponding entry in Plesk? I can only use the domains created in Plesk. This means that I cannot enter the corresponding NS.

My NS entrys in my DNS Zone are set as follows:

Code:
ns1.vlowee-vanlife.de.    A    62.138.14.246
ns2.vlowee-vanlife.de.    A    188.138.25.3
vlowee-vanlife.de.        NS    ns.inwx.de.
vlowee-vanlife.de.        NS    ns2.inwx.de.
vlowee-vanlife.de.        NS    ns1.vlowee-vanlife.de.
vlowee-vanlife.de.        NS    ns2.vlowee-vanlife.de.

The entrys I need should be this for my opinion:

Code:
ns.inwx.de    A    192.174.68.104
ns2.inwx.de    A    176.97.158.104

But these entrys are not possible I think.

What could be the solution here?
 
The warning is indicating that the domain inwx.de does not list the NS records ns.inwx.de and ns2.inwx.de in the parent domain's DNS records.

inwx.de. 21230 IN NS damon.ns.cloudflare.com.
inwx.de. 21230 IN NS dell.ns.cloudflare.com.
 
The warning is indicating that the domain inwx.de does not list the NS records ns.inwx.de and ns2.inwx.de in the parent domain's DNS records.

inwx.de. 21230 IN NS damon.ns.cloudflare.com.
inwx.de. 21230 IN NS dell.ns.cloudflare.com.
Yes I know. But how can I solve this? Plesk has no option for this Glue-Record because inwx.de is not my domain. I can only set A records for my domain. Is there another way to set these entrys in my DNS configuration?
 
I am guessing inwx.de is your registrar. If that's the case, you will need to configure the glue records within inwx.de's portal then remove the NS records for inwx.de since they will not be needed. Either that or just use the DNS services provided by them. The article for setting up a glue record: INWX Knowledge Base - Wie richte ich Glue-Records ein?
 
I am guessing inwx.de is your registrar. If that's the case, you will need to configure the glue records within inwx.de's portal then remove the NS records for inwx.de since they will not be needed. Either that or just use the DNS services provided by them. The article for setting up a glue record: INWX Knowledge Base - Wie richte ich Glue-Records ein?
I've set those entry already. Without these entry's my domain is not reachable.
Please read my first post again? It's all done already. I need to get the missing entry's on my Plesk server.
What do I have to do to correct this error?
 
You will not be setting up glue records on your server but you do need A records created on your server for the entries you're using for the glue records. As long as you have the A and NS records added and you set up the glue records properly with the registrar to have the IPs glued to ns1 and ns2 then it will just work. Likewise you would also want to make sure you have port 53 open for UDP.
 
Last edited:
In addition to @scsa20 ’s reply:

Is vlowee-vanlife.de your domain? If yes,

Are these your server IPs?
  • 62.138.14.246
  • 188.138.25.3
If yes,

In your Domain Registrar, please create these 2 Host Records (Note: There is a specific section for creating these Host Records; they are similar to A records, but not exactly the same):
  • ns1.vlowee-vanlife.de should point to 62.138.14.246
  • ns2.vlowee-vanlife.de should point to 188.138.25.3
Please ensure these records are added to the domain vlowee-vanlife.de.

Additionally, add these name servers to vlowee-vanlife.de:
  • ns1.vlowee-vanlife.de
  • ns2.vlowee-vanlife.de

In Plesk, ensure these are the only name servers configured as your Name Servers.
 
I think I need to formulate my posts a little more precisely. As I wrote in my first post, the website is up and running, it is accessible. There is only this error message that I would like to fix.
My registrar has told me that I have to make these entries in Plesk. But unfortunately this is not possible as it seems. How can I make the following settings in Plesk if the domain does not belong to me, but I just want to make a glue record to an external NS?

Code:
ns.inwx.de    A    192.174.68.104
ns2.inwx.de    A    176.97.158.104

Why do I need this setup? I use DANE and Wildcard in LetsEncrypt and therefore Plesk should be my hidden primary NS. INWX is my secondary NS. The only thing I need to do is the glue-record to INWX. The glue-record at INWX to my PLesk NS is already set and works perfectly. Only the one in the Plesk NS is missing. But there is no possibility to make this entry, because I can only enter my own domains with IP´s. So how can I fix the error?

Thanks for your help.
 
OK there is a disconnect here so let me explain.

First off it's not an error, it's a warning. You're getting that warning because how you're trying to do this will not work since you don't have the authority to provide a zone transfer at the .de level (your registrar). This is why we're helping you set it up for your own NS records ONLY (thus the reason for the Glue Records needing to be set up on the registrar and making sure you have an A record for ns1 and ns2.vlowee-vanlife.de set on your server and having the NS record set on your server as well to point to ns1 and ns2.vlowee-vanlife.de). Once you have the A and NS record set (which should be set by default from the standard Plesk template) and you have your glue record configured with your registrar, you should just use ns1 and ns2.vlowee-vanlife.de and only those, and it should just work as normal. There is not glue record needed on your server since the glue record is needed to be created with the registrar.

As for "hidden primary NS," there isn't such a thing when it's public. You will only find such things on a local network that is not accessible from the public internet. Anything you set for the public internet is shown from the name servers to the IP addresses. If you want to mask some details such as the IP address to your server then you would need to use a proxy service such as Cloudflare but considering you're using NextCloud from what I've noticed Cloudflare only allows so much size to be upload so trying to upload files larger then what Cloudflare allows in it's free service probably won't be enough (you can always pay for a tier that allows for bigger sizes if you know you're gonna be needing it).
 
Ok. Got it now. I deleted the two entrys in Plesk (ns.inwx.de and ns2.inwx.de) and the error is gone.
It was a bit confusing to me because mxtoolbox mentioned that these entry are missing. In the end it was just a propagation issue. I had the correct settings from scratch and added the "missing" entrys as mxtoolbox told me that they where missing.

Thanks for your help.
 
Back
Top