Change FQDN in Snow Leopard Server

I need to change my server from

server-01.local to server-01.xxx.net

The IP address will stay the same, how do i do this ?

Cheers


Andrew
hcshostingAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
heteronymousConnect With a Mentor Commented:
With 10.6 you'll want to use the Advanced install option, and do NOT configure any services during the installation (even though offered). That said, the installation will configure DNS for your server if it cannot lookup your assigned FQDN during the time of installation. So you probably went with something akin to Servername when asked. Instead when asked for the FQDN you'll want to go with that, presuming your server is NOT public facing or if it is, then you DO own the domain in question and have registered it & set that up appropriately.
0
 
heteronymousCommented:
The use of .local would appear to indicate that your server doesn't have working DNS and perhaps lacks a FQDN.

You can change the hostname via:

sudo changeip <ipaddress> <ipaddress> server-01.local to server-01.xxx.net

(man changeip for more info)

You should typically also follow that with:

sudo scutil --set HostName fqdn.tld

but OS X Server must must must have working DNS lookup (forward and reverse).
Make certain to have that in place. DNS needn't be run on the server itself but your existing DNS servers
will need to have forward and reverse entries for your OS X server's FQDN prior to changing the hostname.

On the server itself you can confirm this via:

dig server-01.xxx.net

where of course xxx is appropriately substituted to match the actual FQDN.
and then:

dig -x ip.address.of.server

where "ip.address.of.server" is of course its IP address.

Once you make the change with "changeip"
you should confirm with:

sudo changeip -checkhostname

0
 
hcshostingAuthor Commented:
Thanks heteronymous,

I'll give this a try, do we need to do any config with the open directory or will the above commands do this trick ?

Cheers
0
 
heteronymousCommented:
If your server was already promoted to an Open Directory master, then Kerberos is most probably not working and your services will not be kerberized. But you haven't said enough about your infrastructure (AD involved or not, other relevant details)

In which case you should submit a different question (re: Kerberos). It's possible to rebuild but
if this isn't a production server (hope not, always avoid changing the hostname after putting a server into production, handle this with pre-planning) then you may be best off wiping & starting over. Rarely actually necessary at all with OS X (client or Server) but sometimes easiest when you're new to it.

.
0
 
hcshostingAuthor Commented:
This is a new Mac Mini Server running OS X Sever, we just followed the set-up and all was well. We just followed the set-up instructions and set-up a directory master.  This is the only server in our environment, with only 4 users set-up all accessing via MacBook Pro's.  

Hope this helps..

Cheers
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.