Host name & Networking Setup Hostname

Your hostname should always be FQDN

Your hostname should always be FQDN with the host extention, if in-fact you meant that you are going to change your hostname to the new ip and then rename it to correct hostname. Then that should work but . . . you http conf will have to update and you may need to run the rebuild to make sure that you or it didn't miss.

I always start with Fully Quantified Domain Name with the hostname:

myserver.domain.com

Then I make a host record with my domain name provider so that the DNS works and the name to ip resolves as a host records for nameservers.

-Peter

 

Hi melsworld,

Generally speaking, it's good practice to have a valid host name. Changing it mid-flight won't complicate things, as long as you do it via the WHM. I think the section is under Networking Setup -> Hostname.

Basically, there are MANY advantages to using a valid hostname that points back to your IP. When you deliver mail, this hostname is checked to see if it's not forged or fake. Usually fake hostnames will result in poor mail delivery.

Using a fake host name isn't wrong on non-production servers, as long as mail isn't a priority. Production servers should, in best practice, reflect true hostnames though.

My 0.02$, let me know if you have follow-up questions.

Warmest regards,

 

Yeah, well, the host name can be swapped to anything, as long as it's valid. Just create a "server2 IN A 14400 x.x.x.x" DNS entry and point it to your new server IP in your domain.com DNS zone. It'll be valid, propagated and pointing to the IP so it'll be good... dunno, just a thought. It doesn't have to be identical. The Internets do not know that domains are tied to hostnames. LOL!



J