Mac OS X Server 10.4.11

[Chen]

Greatly appreciate any insights that would lead me towards a speedy resolution of this problem.

I am a single person shop working at home with a Mac Mini running Tiger Server 10.4.11. In my setup, I am running an FTP server (works great for the way I use it), a bunch of other applications that also work fine for my setup. My problem, is that I use a CRM package called Daylite from Marketcircle. They just released their iPhone version of the application and I upgraded my client and server suites to the current level.

This is where my problem begins. My problem is quite simple, while my server setup was not perfect, it suited me fine based on how I needed to work. The Daylite application is now a true client.server app, and as such, needs to function like any trues server/client software. I use DYN DNS to provide me with the ability to use a manual “static” IP on the server so that I can access certain applications when I am on the road. Unfortunately, this solution is not quite as good as it used to be because I know need to be able to use the new iPhone Daylite application on both my WIFI network at home, as well as over the cellular network.

Without going any further, I believe that my problem is a networking one, in that I am stuck in an endless “loop” of not being able to login to my Daylite server using the hostname (mycomputer.green.com). I am able, to do so when I am away from my home office “offnet”, but not when I am on my LAN. In order to connect, I have to use the “static IP address of the server.

I have a Verizon Actiontech router connected to an Airport Extreme, with a small gigabit Ethernet switch off the Airport that supports the server and the other gear in my office.

I need help fixing this DNS resolution problem. I think that is what the problem is, but I do not know how to fix it. I have toyed with changing settings on the Actiontech router, the server, and on the Airport. The one place where I am very week, is on the Mac OS X server – and I think that is where the pain is.

Thanks for any help!
C

[guitar24t]

You need to configure the Tiger server as a DNS itself.
This may require a whole OS reinstall (what Apple says but don’t panic).

Once you have DNS added as a role (my help is limited becuase I use leopard server),
add a primary zone and enter in the primary zone name green.com (for your situation).
expand that primary zone and there should be a machine entry (if not add a Machine (A) record)
in the machine name field, enter mycomputer
then enter the local ip of the machine i.e. 192.168.0.200
go back onto the primary record screen and change the name server to mycomputer (instead of ns).
click save
start the service

open terminal
type
[code]
nslookup mycomputer.green.com
[/code]
It should return an entry with the ip address of the server. If it doesn’t, you will either have to listen to Apple and reinstall from the beginning and give it this host name to start, or give up this feature.
The reason you would have to reinstall is because mac server is garbage and corrupts the local records so that it itself can’t figure out who it’s supposed to be when you change the host name.

if the last step worked, continue:
to be thorough, test the reverse lookup.
in terminal, type
[code]nslookup [server_ip][/code]
It should return the host name (obviously substitute [server_ip] with the local server ip).
if your router allows it, add the local ip of your server as a DNS server on the DHCP tab.
if not, add your server as the first DNS entry manually on your iPhone for your wireless.

try accessing mycomputer.green.com from your iPhone with any kind of service you need.
if you need further help (especially because you have tiger server), just ask.

Cheers,
Robert

[Chen]

Robert, thanks for your last reply. I have been traveling and not giving much focus to this. However, I am now ready to fix this problem if you, or anyone else wish to add additional insights.

My plan, is to migrate to Leopard (because I have to), and then to Snow Leopard as soon as it becomes available. It does appear that Snow Leopard addresses (I hope) many of these DNS issues that have really limited Tiger. Should I wait another couple months or so for Snow Leopard, or go with my two-step migration plan to deal with this? If I move forward now to Leopard, will it be any easier to deal with these type of issues (I have not done much reading on Leopard)?

Thanks!
Chen

[guitar24t]

So far, I have been very impressed with leopard’s server capabilities. I would go with the two-step migration, but before you enable any services, upgrade to 10.5.7. The DNS setup is fairly straightforward if you expand all the drop-down boxes. I can post instructions with pictures if you need them, otherwise follow the instructions in my previous post. Just let me know.
Robert

[Chen]

Hey Robert,

I have upgraded to Leopard, and would appreciate if you can post instructions with pictures.

Thanks!
Chen

[guitar24t]

My guide can be found at [url]http://www.studiosoundandvision.com/OSXDNS/[/url]
Good Luck,
Robert

[Chen]

Thanks for posting such a detailed overview!

I think I will be able to figure it out from here. However, is it important that my Airport Extreme and the Server both have IP addresses in the same range. For example, the router address on the AEB is: 192.268.1.1, while my server’s IP address is: 10.0.1.201. I have actually configured my server pretty much as you outlined, but it is still not quite where it should be, and I am wondering if the number ranges between the router and the server could be the cause of the problem.

Thanks!
Chen

[guitar24t]

Yes, that’s definitely a problem. If the computer is on the network with the airport and the airport is a dhcp server, then it must be in the same range.
Good Luck, Robert

[Chen]

What is the best way to make the change? should I change the computer to the: 192. range, or the airport to the 10. range? I would assume that changing the computer to the 192. range would be easier, but then I would also have to make some changes to the AEB, since I have the server address reserved in AEB under the DHCP tab (DHCP Reservations).

Once I make the changes to AEB, what would I have to do on the server in the DNS tab under Server Admin?

Thanks!
Chen

[guitar24t]

You should change the computer to the 192.168.1.x range and delete the airport base station reservation. Assign the server to a high address i.e. 192.168.1.200. Then, under the DHCP tab of the internet settings, make the starting address 192.168.1.2 (provided that your router is 192.168.1.1) and the ending address 192.168.1.199. There will most likely never be 198+ computers on this single lan and this will also leave space for 50+ static ip’s to be assigned above 199 with no fear of them being taken over.

After you perform these changes, make sure that mac os x server can still access the internet.

As for DNS configuration, I suggest removing the zone that you created and follow my guide from adding a Primary Zone (Master).
Good Luck, Robert

[Author]

Posts