Invalid hostname even though it is valid
Hello,
I want to ask if somebody have this problem and solved it. I have cPanel server which works great, but if server is sometimes restarted during maintenance, emails are not delivered due to 550 Invalid HELO string.
When I checked Change hostname, there's only first name of server from fqdn (so for example only server from server.domain.com).
I already ask about provider about this, and they tell me that server has valid fqdn already set, and they are true, when I put hostname -f I get full server.domain.com. Just hostname return only "server". Which is valid behaviour.
Is it any switch or something to force cpanel to use fqdn name not only first server name?
P.S.: When I changed name in cpanel, it set name of server to fqdn, so everything works, but it shouldn't work like this.
Thanks.
-
After setting the fqdn in WHM Change hostname, check that an 'A' record exists for the servername in WHM>>>DNS functions 0 -
Hello, Please post the output from the following command: grep '' /etc/redhat-release /usr/local/cpanel/version /var/cpanel/envtype ; grep CPANEL= /etc/cpupdate.conf
Thank you.0 -
Hello Michael, here is output /etc/redhat-release:CentOS Linux release 7.2.1511 (Core) /usr/local/cpanel/version:11.58.0.19 /var/cpanel/envtype:virtuozzo CPANEL=release
And here how it looks after restart:root@server [/]# hostname server root@server [/]# hostname -f server.domain.com
When I additionally change hostname via WHM admin then both output are server.domain.com0 -
After setting the fqdn in WHM Change hostname, check that an 'A' record exists for the servername in WHM>>>DNS functions
DNS records are always ok. It's just exim/smtp mail server, it will use only hostname and not hostname -fqdn when sending emails, which result in undeliverable messages.0 -
/var/cpanel/envtype:virtuozzo
I already ask about provider about this, and they tell me that server has valid fqdn already set, and they are true, when I put hostname -f I get full server.domain.com. Just hostname return only "server". Which is valid behaviour.
Could you contact your provider again and have them verify the hostname is properly configured? The information you provided suggests the wrong hostname is stored somewhere on the VPS hardware node or as part of the configuration file for the VPS. Thank you.0
Please sign in to leave a comment.
Comments
5 comments