The following sections help you test your system for DNS functionality and help you resolve any problems that you discover during testing:
In order to access DNS, a workstation must be enabled for DNS name resolution and be configured to locate a valid DNS name server.
From the workstation, ping the servers where you want to install ZENworks Server Management components. Specify the servers’ DNS hostnames, not their IP addresses. If the servers do not respond to the ping command, the workstation might not be configured for DNS. Continue with Enabling a Windows Workstation for DNS Name Resolution.
In order for a workstation to perform DNS name resolution, DNS must be selected in the list on the properties tab.
For example, on Windows 2000:
Right-click (the red N), then click .
Click , make sure that is selected in the box, then click to exit.
A workstation cannot perform DNS name resolution successfully unless it has access to a DNS name server specified on the properties tab.
For example, on Windows 2000/2003:
In the Control Panel, double-click .
Double-click , then click .
Select in the components list, then click .
On the tab, you can choose to let the workstation obtain the DNS name server IP address automatically, or you can specify one or more DNS name server IP addresses manually. For additional DNS configuration options, click , then click .
Select in the components list, then click .
Click , make sure that is listed in the box, then click > > to exit the dialog boxes.
Review the following sections to make sure that a NetWare server is configured properly for DNS:
From the NetWare server console, ping that server’s own FQDN. For example:
ping nwserver3.servers.novell.com
If the ping returns an IP address (192.68.1.203 in this example), forward lookup is functioning. If there is no response from the NetWare server, see Configuring a NetWare Server for DNS.
From a Windows workstation, ping the NetWare server’s own IP address. For example:
ping -a 192.68.1.203
If the ping returns a DNS hostname (nwserver3.servers.novell.com in this example), reverse lookup is functioning. If there is no response from the NetWare server, see Configuring a NetWare Server for DNS.
On the NetWare server, check the sys:\etc\resolv.cfg file to make sure the information it contains is correct.
For more information about DNS on NetWare, see DNS/DHCP Services.
Review the following sections to make sure that a Windows server is configured properly for DNS:
On the Windows server (such as winserver3.servers.novell.com), ping that server’s own IP address. For example:
ping -a 192.68.1.203
If the ping is successful, the domain is configured correctly for that server. If there is no response from the Windows server, see Configuring a Windows Server for DNS.
On the Windows server, ping the the server’s own FQDN. For example:
ping winserver4.servers.novell.com
If the ping returns the server’s IP address (192.68.1.203 in this example), forward lookup is functioning. If there is no response from the Windows server, see Configuring a Windows Server for DNS.
On the Windows server (such as winserver3.servers.novell.com), ping the server’s own IP address. For example:
ping -a 192.68.1.203
or
nslookup 192.68.1.203
If the ping returns a DNS hostname (winserver3.servers.novell.com in this example), reverse lookup is functioning. If there is no response from the Windows server, see Configuring a Windows Server for DNS.
Make sure that the Windows server’s DNS short name is exactly the same as the server name. Also make sure that the Windows server has a DNS suffix.
To check the server name and DNS suffix:
Right-click , click , then click .
The field displays the server name (for example, winserver5), followed by its DNS suffix (for example, servers.novell.com) if one has already been provided.
If the server name does not match the server’s DNS short name:
Rename the server to match the existing DNS entry: On the Network Identification tab, click , edit the field to match the server’s DNS short name, then click .
or
Modify the DNS entry to match the existing server name.
If the field does not include a DNS suffix:
Click , then click .
In the field, specify the DNS suffix for the server.
Click .
Reboot the Windows server to put the new server name information into effect.
Check the \winnt\system32\drivers\etc\hosts file to make sure that the information listed in it is correct.
For example, you must have a local host entry pointing to 127.0.0.1, which the facilitator requires for communicating with ZENworks Web Server.
For more information about DNS on Windows, refer to Windows online help about using the DNS administrative tool.
Review the following sections to make sure that a Linux or Solaris server is configured properly for DNS:
From the Linux or Solaris server, ping that server’s own FQDN. For example:
ping unxserver3.servers.novell.com
If the ping returns an IP address (192.68.1.203 in this example), forward lookup is functioning. If there is no response from the Linux or Solaris server, see Configuring a Linux or Solaris Server for DNS.
From a Windows workstation, ping the Linux or Solaris server’s IP address. For example:
ping -a 192.68.1.203
Or from the Linux or Solaris server, use:
nslookup 192.68.1.203
If the ping returns a DNS hostname (unxserver3.servers.novell.com in this example), reverse lookup is functioning. If there is no response from the Linux or Solaris server, see Configuring a Linux or Solaris Server for DNS.
On the Linux or Solaris server, make sure that the /etc/hosts file has the correct IP address and FQDN for itself. Make sure that the loopback address line (127.0.0.1) reads localhost.localdomain, not the server’s FQDN.
For more information about DNS on Linux or Solaris, refer to your operating system documentation.