Hosting wikis on mac server - dns problems

[reggiep]

Ok, I thought i'd try and utilise our mac server a bit more and set up a website from it so the staff could use the wiki feature to share teaching practices.
My downfall seems to be that I can access the server from a workstation by typing mac-1 in the address bar from one domain but the other I have to type the ip address in 10.60.*.*. Also I have an external IP address pointing to it so I can type 212.248.*.* and that will work to.
My problem starts to appear when A user tries to click on a wiki link and then it breaks.
The webserver is looking for http://mac-1/groups/wiki and when a user clicks on to it after browsing to it from the ip address it will look for 10.60.*.*/groups/wiki and fails.

Does anyone know how I could get round this?

Would I need to change a file somewhere in the backend or create duplicate sites from server options or something else?

Thanks

[FN-GM]

You need to create a DNS name for it

eg: wiki.school.com

then you need to point your internal and external DNS settings to point to the server. you might also need to change the settings in the WIKI software to point to the DNS name

[reggiep]

The thing is I have added a dns entry on both domains!
To access it externally I guess I might have to buy a domain name, and then i suppose I can add that domain name to the mac server so I can then access the site both externally and internally from the registered domain name eg. prentonwiki.org?

[reggiep]

OK, FN-GM I take it back.
I had not created a dns entry on the mac server itself. I did that and now it works on all domains, macs and pcs BUT I can't get it to work from outside the school.

Mac OS X Server is my public address to the site.

I can browse to that but if I click on a wiki group it bums out.
I'm guessing that I need to register a domain name and then re-jig all my internal dns to point to that.

[HodgeHi]

I think that this is due to the dns name. The wiki service on a mac is not the best implemention to set up. It needs to be able to resolve the FQDN of the server. Ideally you would want the server name to be www and in a domain name that you own eg example.com. This allows external sites to find your server and then your server to resolve it's own name and find your user groups. I think that's how it works.

Or course I may just be talking twiddle.