• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Resolved nameserver configuration goes wrong

TomE

Basic Pleskian
Hello,

I'm trying the nameserver right now and fail.

My hoster is Starto and there I have set in the KIS as primary nameserver my registered ns1.mydomain123.de and as secondary the one of Strato sns.serverkompetenz.de.

When I test it online with mx tools I get the message "Sorry, we couldn't find any name servers for 'mydomain123.de'".

In Plesk I used the default DNS template. The bind process is running and the port is open. There is no error message in any logfile.

With an nslookup I get

Code:
# nslookup mydomain123.de ns1.mydomain123.de
nslookup: couldn't get address for 'ns1.mydomain123.de': not found

Code:
# nslookup mydomain123.de sns.serverkompetenz.de
Server:         sns.serverkompetenz.de
Address:        2a01:238:10a:2300:2:1:51a9:9426#53

Name:   mydomain123.de
Address: 81.169.209.114
Name:   mydomain123.de

i know the problem is not a plesk problem but a problem with me :( maybe somebody still has a tip for me?

Thanks an regards, Tom
 
In cases like this, it would really help if we knew the real domain name so that that the whois and DNS can be queried.
 
Hi Ales,

Thank you for your answer but the problem is solved. The zone transfer simply took longer.

Best regards, Tom
 
Back
Top