Home › Forums › OS X Server and Client Discussion › Questions and Answers › Migrating 10.3.9 to 10.5
- This topic has 3 replies, 3 voices, and was last updated 15 years, 10 months ago by
foilpan.
-
AuthorPosts
-
April 25, 2009 at 8:33 am #376064
implex
ParticipantHi guys,
Firstly – great forum been an invaluable resource for me at the moment setting up my first OSX server.
[b]Background[/b]
I have a 10.3.9 server that was setup for our home office a while ago and has been running fine. Recently decided to move up to 10.5 especially for some of the new features (calender, etc.)
I have managed to do some training DVDs and have a general understanding of server and its workings. Also read the Apple PDFs that are relevant.
The 10.3.9 is the only server. It’s in an Advanced configuration and is the Open Directory master.In migrating there is no new/changes to physical configurations. I am hoping to straight swap with the new server once configured.
[b]Problem[/b]
On the 10.5 machine i am setting up I can’t promote the standalone machine to the Open Directory Master. I’m certain its due to my lack of knowledge of DNS. I was hoping that someone would be able to point me in the right direction of how to setup. (I’m at a loss to names/PTR records machine records etc)[b]Relevant Info[/b]
On the 10.3.9 machine ‘hostname’ in terminal returns: silver.dizign.com.au
DNS Server is 192.168.0.1
Machine name is silverresolv.conf file
[code]
domain nsw.optushome.com.au
search nsw.optushome.com.au
nameserver 203.2.75.132
nameserver 198.142.0.51
nameserver 203.2.75.132
nameserver 198.142.0.51 //not sure why this appears twice
[/code]named.conf file
[code]//
// Include keys file
//
include “/etc/rndc.key”;
// Declares control channels to be used by the rndc utility.
//
// It is recommended that 127.0.0.1 be the only address used.
// This also allows non-privileged users on the local host to manage
// your name server.//
// Default controls
//
controls {
inet 127.0.0.1 port 54 allow {any;} keys {
“rndc-key”;
};};
options {
directory “/var/named”;
recursion true;
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};//
// a caching only nameserver config
//
zone “.” IN {
type hint;
file “named.ca”;
};zone “localhost” IN {
type master;
file “localhost.zone”;
allow-update { none; };
};zone “0.0.127.in-addr.arpa” IN {
type master;
file “0.0.127.in-addr.arpa.zone”;
allow-update { none; };
};logging {
category default {
_default_log;
};channel _default_log {
file “/Library/Logs/named.log”;
severity info;
print-time yes;
};
};
[/code]Any help on how to make sure my 10.5 server is setup correctly is appreciated. If you need any more info let me know and I’ll happily obtain! Thanks 🙂
April 29, 2009 at 1:43 pm #376089implex
Participant🙁 No love.
May 1, 2009 at 1:18 pm #376101tlarkin
ParticipantI am no expert, but in server 10.5 it uses the [color=Blue]changeip[/color] command to resolve DNS. So make sure your DNS is in order, and if it is not you may have to destroy LDAP and rebuild it. To do so run this
ssh into your ODM
changeip -checkhostname
May 29, 2009 at 4:32 pm #376333foilpan
Participantyou’ve probably already migrated your server, but i recommend NOT upgrading from 10.3.x to 10.5.x server. too much has changed. you’d be better off doing a clean install.
also, be sure you get dns configured on the new server. without proper dns resolution — either provided by your 10.5 server or elsewhere — OD won’t work properly.
configure dns first on the new server and then move onto the rest of your services.
-
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed