Check DNS Setting before Lion Server Open Directory Deployment
If, during your initial Lion Server setup, you configured Server Assistant so that it created an Open Directory master for you, it should have also set up DNS. If you didn’t do this configuration during initial setup or have a DNS server running on another server, you’ll need to ensure that DNS is configured to support Open Directory.
Properly configured DNS is critical to the configuration and normal operation of an Open Directory domain. All Open Directory servers need static IP addresses, a zone with the host domain name, and two types of records: a fully qualified DNS address (A) and pointer (PTR) records. Verify the server’s DNS records prior to promoting a Mac OS X Server to either master or replica status.
In an A record, also called a machine record, the system’s hostname is resolved to an IP address. That is, when another computer requests the IP address for a given domain name, the machine record supplies it. A pointer (PTR) record, also known as a reverse lookup, resolves a domain name for any given IP address. Reverse resolution inquires about an IP address and returns the hostname.
By default, the domain’s LDAP search policy and Kerberos realm are the same as the fully qualified hostname of the Open Directory master and are generated when a server’s role is changed to master. Without correct DNS records, promotion to an Open Directory master or replica will likely fail or create only a partially functional domain.
If you don’t mind typing a one-line command in the Terminal utility, you can easily verify that DNS forward and reverse lookup are configured correctly. Type this, exactly:
sudo changeip -checkhostname
If forward and reverse DNS are working correctly, you see this, but with your server information:
Primary address = 192.168.1.69 Current HostName = ourserver.macwindowsco.com DNS HostName = ourserver.macwindowsco.com The names match. There is nothing to change. dirserv:success = "success"