Home › Forums › OS X Server and Client Discussion › Open Directory › redoing open directory
- This topic has 4 replies, 1 voice, and was last updated 19 years, 7 months ago by
mgaslowitz.
-
AuthorPosts
-
April 10, 2007 at 7:42 pm #368722
mgaslowitz
ParticipantAbout a year ago I was given the task of setting up my firm’s new Xserve as an Open Directory Master (without reading aft548.com), and knowing nothing about the importance of reverse DNS. For the most part the server functions well, but things go wonky from time to time, so I’d really like to knock the server down to a Standalone Server, configure DNS properly, and promote the server back to its rightful Master status.
Is there a safe way to do this while protecting 25 network users (home folders) and their hosted imap accounts and messages? Passwords are trivial in all of this.
Thanks for any help and suggestions!
Michael Gaslowitz
mgaslowitz@gadisputes.comApril 13, 2007 at 1:24 pm #368754mgaslowitz
ParticipantWicked. Thanks guys.
April 15, 2007 at 2:10 pm #368762mgaslowitz
Participanton the off-chance someone will look at this on a Sunday…
So the server has two ports:
public 65.202.106.66
private 192.168.2.1running “sudo change ip -checkhostname” from the server returns
Primary address = 65.202.106.66
Current HostName = gadisputes.com
DNS HostName = gadisputes.comrunning “host 192.168.2.1” from a client returns
1.2.168.102.in-addr.arpa domain name pointer xserve01.gadisputes.com.running “host xserve01.gadisputes.com” from a client returns:
xserve01.gadisputes.com has address 192.168.2.1When I went to promote the server to Master is wanted the realm to be “GADISPUTES.COM” and through these efforts have used that and also “XSERVE01.GADISPUTES.COM” but the results are always the same…
I cannot get the clients to bind to the directory and AFP won’t work at all.
I can access the server with SSH, FTP, webmail, ect using local and hosted accounts, but any attempt at using a network login or command-k (connect to server) brings AFP down.
Help.
April 15, 2007 at 5:36 pm #368763mgaslowitz
ParticipantApril 16, 2007 at 2:02 pm #368765mgaslowitz
ParticipantHaving the server manage both the public and private was the headache (and obviously not the most secure), so I dropped the server behind a external firewall (which now has the public ip), giving the server only a private ip with dns working properly, open directory singing, and clients machines binding left and right.
-
AuthorPosts
- You must be logged in to reply to this topic.