Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Install and Configure Snow Leopard Without Static IP Address

The following instructions are for installing Snow Leopard Server and configuring DNS service without a static IP available. They may be used to set up Snow Leopard Server for small businesses or home networks which obtain Internet service from ISPs via cable modem, DSL, etc.

The instructions were drawn from recent experience of installing Snow Leopard Server on a Mac Mini on our network, which receives Internet service from Starhub in Singapore. A big thank you to Todd and Don from Apple ProApps support, who helped with the setup.

The instructions assume a router which is an Airport/Airport Express/Time Capsule.

_Step 1: Install Snow Leopard Server_

Recommendations: Boot up from Snow Leopard Server DVD (hold option key when starting up machine). Initialise hard disk (use Disk Utility) and install Snow Leopard Server fresh.

Welcome: Select Country or Region
Keyboard: Select Keyboard Layout
Serial Number: Enter Serial Number
Transfer an Existing Server?: Select "Set up a new server"
Registration and A Few More Questions: Enter Registration Information (2 screens)
Time Zone: Select Time Zone and Network Time Server

_Administrator Account_
Enter information to set up an Admin account locally on the server. Recommendation: use a name - or at least a short name - that is different from any accounts set up on client machines.

_Network screen - Important Step!_
Configure IPv4: enter Static IP (use 192.168.1.192) or make sure DHCP reservations are set up on Airport to always dish out 192.168.1.192 to server

IP Address: 192.168.1.192
Subnet Mask: 255.255.255.0
Router: 192.168.1.1
DNS Server: 192.168.1.192, 192.168.1.1
Search domains and DHCP Client ID may be left blank.

Important: DNS server field will be "pre-filled" with gray IP addresses. Make sure these are overwritten with DNS Server information as set out above. Do not leave the field blank.

Airport Management: Allow Mac OS X Server to configure Airport - tick "Enable AirPort automanagement for "Airport name"" and enter Airport admin password

_Network Names screen - Important Step!_

This screen may take some time to come up - be patient

Screen will say at bottom "No DNS name was found for this computer. This server will provide its own limited name resolution so that services operate properly"

Enter the following in the fields:

Primary DNS Name: servername.companyname.private
Computer Name: servername

Note: "private" can be anything e.g., "llp" or "company"; servername is the name you want to give to your server. So the Primary DNS Name could be for example "plato.jacksonsgroceries.limited" with the Computer Name being "plato"

Users and Groups: select "Create Users and Groups"

Services: tick whatever services you want your server to provide

Client Backup: tick if you want client computers to make Time Machine backups to disks connected to the server

Mail Options: set up mail server

Review: Click Details… to save configuration information

Click "Set Up" to complete - this may take some time.

Server will boot up to Server Preferences. Close this. It may also ask if you want to use any connected disks as Time Machine backups.

Install any updates using Software Update.

_Step 2: Configure DNS Service on Snow Leopard Server_

Make sure Server Preferences is closed and launch Server Admin. It should log you into the local server automatically. If not, add the server, if necessary using 192.168.1.192 and login.

Click on DNS on the left hand panel. If DNS is running (green dot), click "Stop DNS" at bottom of screen.

Click Zones at top of right hand panel. Read the warning and dismiss it.

Note the Type column. There should be a "Primary Zone" entry and a "Reverse Zone" entry.The "Primary Zone" entry should have the name of your "Primary DNS Name" set up above, with a trailing full stop (i.e., servername.companyname.private.). Select it and click on the disclosure triangle on the left. A record of type "Machine" should appear.

Click and select the Primary Zone entry. Make sure the settings are as follow (do not click Save until the last step below):

Primary Zone Name: companyname.private.
Admin Email: [your email address]

In the Nameservers area below:
Zone: companyname.private.
Nameserver Hostname: servername.companyname.private.

Important: Note the trailing full stops - they must be included

Mail Exchangers: ignore this

Go back to top of screen and select the Machine record you expanded earlier. Make sure the area below shows the following:

Machine Name: servername.companyname.private.
IP Addresses: 192.168.1.192

Click "Save" to save the DNS settings. Click "Start DNS" to start DNS service.

_Step 3: Check DNS Settings are Correct_

Check that everything is set up correctly by using the Terminal:

hostname


the answer should read:

servername.companyname.private


If you want to double check your DNS run the following command:

sudo changeip -checkhostname


You will be prompted for a password. Enter your admin password (no characters will appear as you typed it due to masking).

the answer you will receive should be this:

Primary address = 192.168.1.192

Current HostName = servername.companyname.private
DNS HostName = servername.companyname.private

The names match. There is nothing to change.
dirserv:success = "success"

_Step 4: Configure Mac OS X Clients_

For the client systems go into System Preferences > Network

For Ethernet select the Ethernet port and switch DNS servers to the ones above, i.e., 192.168.1.192, 192.168.1.1

For Airport select Airport, then select advanced on the lower right, then select DNS tab and enter them there.

Macintosh SE/30, Mac OS X (10.6)

Posted on Sep 7, 2009 11:39 PM

Reply
22 replies

Nov 1, 2009 6:44 PM in response to Chong-Yee Khoo

Been looking all over for instructions on how to setup Snow Leopard Server without a static IP address. (As I like most all home users have a dynamic IP) from my ISP. I use Dyndns.com that continually checks to make sure the local IP address is set to a hostname they provide such as example.homeip.net.

I read through your instructions and it certainly explains how to setup the server internally, but I don't see the part about having a dynamic IP. Was the Title of the post and error or am I missing something?

Would I swap servername.companyname.private for example.homeip.net? Or do I enter in servername.companyname.private and after the install somewhere I would enter example.homeip.net?

I saw others from comments with the same confusion but didn't see a response from the author. Thanks in advance!

Nov 3, 2009 8:15 AM in response to asilverpeach

I am in the same situation. I just bought a miniserver and struggling a bit to set it up. My needs are simple enough, but the manuals on the Apple website do not give me the information I need to go ahead and set this up with confidence.
I have a list of things I need answers to. One is I am currently running a small website on a eMac.
The current set up: Internet - DSL modem - AE - eMac.
I have a dynamic IP, but I run DynDNS updater on the eMac to refresh the DynDNS IP table. AE has port 80 open and points to the IP address of the eMac on my LAN. That has been working flawlessly.
I want to move that website to the miniserver. I see two options , either I just copy the website files tot he same folder on the mini and have port mapping on the AE to point to the mini IP. I would install DynDNS updater on the mini to keep track of the IP address (I plan to shutdown the eMac). Option 2 would be to change the Primary DNS network name of the mini to a .com address, as it seem to be inferred in the manuals, but I have no idea on how to complete the setup this way, or if it would actually work given that the AE is the interface to the WAN.
In the future, I would like the miniserver to host more than one website.
I have come to think that in my configuration, the Primary DNS network name on the mini is strictly for the LAN, but would like to have this confirm as I plan to access this server from the outside in the future; probably the subject of a future post.

Nov 3, 2009 11:43 AM in response to Chong-Yee Khoo

Results to follow up my previous post.
I started the web services on the mini and added a custom web site with my registered web site name. The files were put in Library/Webserver/Sites/mysite.
Changed the settings in AE to map port 80 to miniserver. Installed DNS updater on miniserver.
Could not connect to my registered domain name. This one is forwarded to my dyndns domain.
To my surprise, typing my dyndns domain name in safari opened my website.
I then played with aliases in server Admin, but was never able to get my registered domain to open. I always get "canceled open" when looking at the activity window in Safari. I moved everything back to the eMac, and like previously, am able to access the site with the dyndns domain name and the registered website name.
I wish someone can explain how I can get the mini to accept my registered domain name.

Nov 8, 2009 11:23 AM in response to ongillem

I'm writing to express thanks for relief from pain and suffering by wiping my initial install of Snow Leopard Server, and starting over with the guidance laid out above. I'm hoping my experience will save another lost soul.

I have little experience working with servers, but took the bait with the new mini server, as I expect many other home users will. Set up of this is not intuitive, and requires more thought than an adept mac user, but server neophyte(me), might expect. My biggest error was in not understanding my ultimate goal, or the implications of my set up particularly regarding DNS and a local address. Using my airport extreme with the mini controlling it seemed a natural. **** started when I allowed the server to takes its name from the IP address set up for the cable modem by comcast. Trying to correct the DNS with scutil commands and terminal left me with a week of pain, and no resolution of the DNS hostname.

Reinstallling the server software let me walk through this relatively unscathed. Surprisingly, even after walking through the set up described above, the DNS is not filled appropriately with information for managing the server, and DNS must be manually reconfigured as described above after the initial network set up. I would urge those with similar set ups behind an Airport extreme with DNS problems to consider the same unless you're already in too deep.

Dec 2, 2009 4:31 PM in response to Chong-Yee Khoo

Hi All,

Very nice post. I am planning to configure my mac mini soon and I'm sure this will be extremely helpful. I have afew side and extra questions to put out there:

(1) Will this method allow for file sharing from outside the local network? This is really what I want my mac mini to do (act as file server).

(2) Does anyone have thoughts of having the mac mini connected directly to the router versus wireless? In addition to file sharing it would be nice if the server could be used for streaming (probably music mostly).

(3) How many of these steps can be performed after the initial setup? I am planning to switch over to cable from DSL in the next few months and don't want to reformat my drive again.

(4) Any thoughts on 'cool' things to do with the mac mini server besides file sharing. My ultimate goal is to use this as a source for movies and music from family members (spread across the country) to access and contribute to. I would be interested to hear what applications you guys are using the server for.

Thanks!

Install and Configure Snow Leopard Without Static IP Address

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.