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

Problems with hostname resolving

mark0134

New Pleskian
Hi everyone. Let me explain my problem:

I have two OVH servers (server1, server2) with their reverse DNS records (set in the OVH control panel), let's say "server1.myservers.net" and "server2.myservers.net". Both resolve properly from any machine to their corresponding IPs.

Now, from server1 i can resolve server2's hostname (server2.myservers.net), but the opposite doesn't work: doing "nslookup server1.myservers.net" from server2 returns a NXDOMAIN 'cannot find' error. Both servers are using Plesk's BIND DNS service. If I use an external DNS server to perform the lookup, it resolves properly. Also, 'myservers.net' is resolved correctly on both servers. The firewall is turned off on both servers.

Adding the line "222.222.222.222 server2.myservers.net server2" to /etc/hosts in server1 doesn't change anything either. (assuming 222.222.222.222 is server2's IP)

Does anyone know why this happens?

(Please note all the names and IPs are hypothetical and aren't actually real)

Thanks in advance!
 
Last edited:
Back
Top