Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

quick question:

let's say you have a ssh login computer called sshlogin.example.com. Now for some obscure reason, your company decided to rename that machine to ssh.example.com. What's the best practice here? should I generate new ssh keys for that machine? Alternatively, should I just keep the old ssh keys?

EDIT1: one could imagine that whoever decided to rename the machine in the first place, might change his / her mind. so ssh.example.com might become sshlogin.example.com after a while again. Maybe this should be considered?

EDIT2: what if the IP address would change? what's the suggested procedure?

share|improve this question
1  
If the IP address changes, clients will perceive it as a new host. This will cause problems with the stored keys. –  adaptr Feb 1 '13 at 19:37
add comment

closed as not constructive by SvW, mgorven, mdpc, Khaled, Michael Hampton Feb 2 '13 at 22:41

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

1 Answer

up vote 2 down vote accepted

I'm not sure about what best practice is, but I'd be tempted to keep the old SSH keys. It's the same service, actually on the same machine, and will probably have the same IP. To me, the "rename" isn't changing anything sufficiently to justify a new set of keys.

share|improve this answer
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.