Issue Made a mistake, changed server hostname, please advise

[elliotpa04]

Server operating system version

Ubuntu 24.04.4 LTS

Plesk version and microupdate number

18.0.79

Complete amateur apologies in advance. I had a conversation with the server provider about some email deliverability issues and he advised me on setting up rDNS. Part of that discussion was for me to change the server host name in Plesk which I did. I asked the person in control of the domain to add a corresponding A record but that didn't happen which I think has resulted in some issues - any external connection from plesk is failing - SMTP Backup time out, 'Whats new' News feed in the dashboard timing out, emails all deferred with 'host not found'. Also and most important website hosted on the server is giving 504 gateway timeout.

Ive made a big mistake, and to try to rectify I have reverted the server host name to what it was. Not had an effect yet but the original change didn't result in issues for some hours.

So, have I done the right thing reverting to the previous host name? Is there anything else I could or should be doing? Any advice appreciated.

 

[Sebahat.hadzhi]

Hi, @elliotpa04 . Since the other domain name isn't pointed to the server, reverting the hostname back to the original one makes perfect sense. When you say it hasn't had effect yet, could you please confirm which of the issues are still remaining? Can you please execute the following command and confirm if you are able to reach Google from the server:

curl -I https://www.google.com

 

[elliotpa04]

Hi, @elliotpa04 . Since the other domain name isn't pointed to the server, reverting the hostname back to the original one makes perfect sense. When you say it hasn't had effect yet, could you please confirm which of the issues are still remaining? Can you please execute the following command and confirm if you are able to reach Google from the server:

curl -I https://www.google.com

Sorry for the late reply @sebahat-hadzhi and thanks very much for you input. Ultimately the issues I faced were not related to the change in host name, that was an unfortunate coincidence which led me down the wrong path. In fact what had happened is the connection between the server and the network failed and the hosting provider had to resolve it. Your suggestion is in fact what led to this realisation:
dig google.com: communications error to 212.227.123.16#53: timed out
So thanks very much indeed.