• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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