Error message in log... What is it and how can I fix it?

Hi

On the server launch terminal and issue this command:

sudo changeip -checkhostname

Post the result. Hope this helps, Tony

Hi

Is the Server Standalone? If so run this command

sudo changeip - 10.31.3.135 10.31.3.135 KNWS3135 KNWS3135.ad.ewsad.net

enter the password when prompted and restart the server.

If the Server is an Open Directory Master issue this command:

sudo changeip /LDAP/127.0.0.1 10.31.3.135 10.31.3.135 KNWS3135 KNWS3135.ad.ewsad.net

enter the password when prompted and restart the server.

Before you do this can I ask if the DNS Service is being provided by an Active Directory Domain Controller? In other words a Windows Server. If it is and the Windows System Admin has created a DNS entry for your server then make sure there is a Reverse Pointer entry for your server. Make sure the Windows System Admin uses the KNWS3135.ad.esad.net as the FQDN (fully qualified domain name). Enter the AD Server’s IP address as the Primary IP Address in the DNS Server Field on your server and then issue this command:

host KNWS3135.ad.ewsad.net

You should see something like this:

KNWS3135.ad.ewsad.net has address 10.31.3.135

follow this with:

host 10.31.3.135

You should see something like this:

135.3.31.10.in-addr.arpa domain name pointer KNWS3135.ad.ewsad.net.

If you are seeing this after you have made sure the Windows System Admin has created the relevant PTR entry for your server then issue the changeip command again:

sudo changeip -checkhostname

This time it should report 'the names match there is nothing to change'

Hope this helps, Tony

Hi Bruce

Its always a good idea to let an AD Server know of other servers on the same network especially if you are planning to integrate and augment AD with OD.

At some stage you must have asked the AD System Admin guy for an IP address - presumably the AD Server is also the DHCP Server? It would be at that stage that the request for a PTR entry should have been made.

How does the AD System Admin guy do this? He/She creates the relevant entries in the forward lookup zone using the DNS Snap In module on the AD Server. Once he/she does that a PTR entry can be made for the NS and A records in the Reverse Lookup Zone.

Hope this helps, Tony