Why do I keep getting this message on my VPS?

[Latona]

FROM: cpanel@myserver.mydomain.com

IMPORTANT: Do not ignore this email.
The hostname (myserver.mydomain.com) resolves to xx.xxx.xxx.xx. It should resolve to yy.yyy.yyy.yy. Please be sure to correct /etc/hosts as well as the 'A' entry in zone file for the domain.

Some are all of these problems can be caused by
/etc/resolv.conf being setup incorrectly. Please check this file if you
believe everything else is correct.


You may be able to
automaticly correct this problem by using the ' Add an A entry for your
hostname ' under ' Dns Functions ' in your Web Host Manager

The background is that I had originally got a VPS Hosting and had it the IP changed due to problems with the first one.

Ok, I get the message every day at around 5:50am. I have previously checked in my web host manager and can not find any reference to the previous IP address. Originally it was set up with the first IP address and was changed for the new IP address by eukhost.

I have raised at least 2 tickets - both claiming that it had been fixed, but still I receive the messages.

I am asking here, as maybe someone will be able to help - it is just annoying that I keep getting the email and it also shows on the logs as executing a cron script - the same script that is called by the new IP.

[Rsync]

hello,

This problem persist, if the hostname's A record is not pointing to the correct IP. Also there is some entries for the hostname if it's not correct then this error persist. Can you please open a support ticket regarding this issue or let me know the ticket number on which you have mentioned this problem or your email address using which I can find your VPS Hosting, so that I will make the necessary changes for you.

[Latona]

[#HJS-78858-933] - It had been resolved/fixed by 2 seperate people... but it actually kept doing the exact same.

The original first occurrance was on 07/08/07 - the day after named, httpd, ftpd and cpsrvd failed. Previously the problem did not exist. I didn't alter records during that time, but since the 07/08/07 I have received a daily email.

[eUKhost.com]

Please send ping request to hostname of your server from your command prompt and check if it resolves to your server or not.

I am quite sure that your hostname is not resolving and thats the reason you get this error again and again. Your domain name in your hostname must be resolving from some different server and you will need to add A record of hostname on that server.

[Rsync]

Hello,

I have investigated your issue and found that we had transferred your VPS Hosting from one node to our new node, but both VPS Hosting's are running so proablly you got the notification from the old VPS Hosting, "aaa.bbb.ccc.ddd" is the Old VPS Hosting ip address and "www.xxx.yyy.zzzz" is the new VPS Hosting ip address and The error messages you receive is like this,

IMPORTANT: Do not ignore this email.
The hostname (myserver.mydomain.com) resolves to "www.xxx.yyy.zzzz". It should resolve to "aaa.bbb.ccc.ddd". Please be sure to correct /etc/hosts as well as the 'A' entry in zone file for the domain.

Some are all of these problems can be caused by
/etc/resolv.conf being setup incorrectly. Please check this file if you
believe everything else is correct.


You may be able to
automatically correct this problem by using the ' Add an A entry for your
hostname ' under ' Dns Functions ' in your Web Host Manager

The error messages clearly show that the hostname is pointing to the correct IP.

As both VPS Hostinges are in running status (old VPS Hosting might have started because of vz service restart or it must have been kept running so that you dont face any down time in propagation period after migration) due to which all the error email which you were receiving are from your old VPS Hosting. Not from your new VPS Hosting. I have stopped your Old VPS Hosting and you will not receive error messages any more.

[Latona]

Thanks Ramon, that sounds like that could have been the reason - and why I couldn't find any reference to the original IP anywhere.

I had got used to receiving the daily emails - but I thought it had gone on long enough and again aimed at resolving it. Hopefully, next time I check my email I don't find that message.