Ask Different is a question and answer site for power users of Apple hardware and software. 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

Our Mac OSX servers sends me this message every day:

Name: System Administrator
Dept: Support

The host name of SERVER1 has changed to SERVER2. Some services may not work correctly until they have been updated to use the new configuration.

(in which, SERVER1 is the old host name and 2 the new host name of our server). What does it mean, and what could I do to solve this (get rid of this message). The server seems to work just fine, just as it did before.

share|improve this question
You're right, I've edited the question! – tvgemert Jun 27 '12 at 8:54
Have you rebooted the server since the name change and where did you change the name? – Mark Jun 27 '12 at 9:04
Yes, it has been rebooted since. – tvgemert Jun 28 '12 at 10:19
Have you found the reason for this? – nicktmro Sep 9 '12 at 2:16
No, sorry haven't found it. In the meanwhile we set up a new server so this old situation is not bugging us anymore. – tvgemert Sep 12 '12 at 15:47

If your hostname changes regularly, you can suppress the notifications by opening, going to AlertsDelivery and disabling the Network Configuration alert (for Email and/or Push).

Server Alert Settings

share|improve this answer

I was having the same problem & found this thread on Apple Support Communities.

The short of it is that unless the name change is done through the command line with sudo changeip, it will forever complain about the change. The command goes like this:


Use the same IP address and name in both spots and it's happy.

share|improve this answer

Shutting off the Network Configuration (change) alert is the equivalent of putting electrical tape over the "Check Engine" indicator on your car. You are simply ignoring a an important warning.

Changing the IP address or the hostname on OS X server has always been a bad idea. Both are foundational to Open Directory working properly, just for one important example. The hostname gets "baked" into 8-12 configuration files. Changing the hostname in one location can create a mismatch in all the other locations. So don't ever change it unless you have a really important reason! And if you must, then you should use changeip to do so.

The changeip command ensures that the hostname is set up properly across all locations.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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