Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

quick question:

let's say you have a ssh login computer called Now for some obscure reason, your company decided to rename that machine to 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 might become 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

closed as not constructive by Sven, 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.

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
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

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