That will break something.
You need to also use the changeip command. Something like:
sudo changeip /LDAPv3/127.0.0.1 10.100.1.11 172.16.21.11 flower.example.com ldap.example.com
Make sure that the DNS and reverse DNS for (new and old) hostname and IP exist before running this command. I would use the following commands and make sure there are no errors:
host 10.100.1.11
host 172.16.21.11
host flower.example.com
host ldap.example.com
Also note that it does not actually change the IPs, you still need to use the GUI or networksetup and systemsetup commands to make the actual changes. And even if the name is not changing, still put it in the command line like so:
sudo changeip /LDAPv3/127.0.0.1 10.100.1.11 172.16.21.11 flower.example.com flower.example.com
and then check via:
sudo changeip -checkhostname
Also, for me, when I changed the IP and name of my OD master, most of my clients locked up (could not login to them) and I had to reboot all of them to fix the problem. Netstat -a showed sockets to the ldap server on port 389 in a SYN_SENT state, so maybe there is a way to force the machine to try and reconnect to the OD master, but I could not figure that out short of a reboot. Has anyone else seen this? Any suggestions on how to avoid rebooting all the other servers on the network?
Recent Comments