Library Table of Contents Index Previous Next Comments

Joining the domain without using DNS

Circumventing DNS  Top

You can configure the NetCache appliance for deployment in enterprise environments that require the appliance to authenticate to Microsoft Windows 2000 without using DNS as a name server. For this type of deployment, the appliance does not use the Server Message Block (SMB) over port 139 to maintain its machine account within the Microsoft Windows 2000 domain. (However, it can use the SMB port to authenticate clients. SMB is used for communication between hosts.) Instead, the appliance uses LDAP and Kerberos to maintain its machine account, and it is for this reason that the appliance must know their location.

Given these circumstances, the appliance must be able to locate the Microsoft Windows 2000 Kerberos and LDAP services. Recall that Kerberos is used to authenticate hosts and users (in this case, the NetCache), and LDAP is used to provide generalized access to domain information.

The DNS server stores the locations of these services in special records called Service Location Resource (SRV) records. These records allow a network to register its location and services with DNS, which then queries the records for the location (IP address) of a service when it is required.

This section describes how you can override use of DNS in joining the appliance to the Microsoft Windows 2000 domain by specifying the IP addresses and other information for Microsoft Windows 2000 domain account setup.

Requirements if not using DNS  Top

Joining the NetCache appliance to a Microsoft Windows 2000 domain without using DNS requires that you identify a set of hosts that export services required to join the domain and authenticate the appliance to it.

Windows 2000 servers can export any of four types of services, shown in the following table. For each of these services, special records are stored in DNS that a Windows 2000 host uses to locate the servers exporting the services it requires. Because DNS is not available, the NetCache must specify information about the hosts as shown in the following table.

Host type

Service record

Active Directory

LDAP

Kerberos Key Distribution Center

KDC

Kerberos Admin

kpasswd

SMB

DC

Note
Most often all of these services are exported by the same host.

Kerberos  Top

The NetCache appliance authenticates itself to the Microsoft Windows 2000 domain using Kerberos authentication. Kerberos is based on a ticket-granting service, which runs on a Kerberos Key Distribution Center (KDC). The KDC provides session keys for authentication, authenticates the client and server, and grants tickets which assert the user's identity and include other security data. Among the information you must provide are addresses to the KDC and Kerberos password servers to be used.

You can join the appliance to the domain using either the Appliance Manager or the CLI (see Procedures and option descriptions).

To join a Microsoft Windows 2000 domain without using DNS, you must provide the following information.

Information

Required to...

Specified from...

Windows 2000 Domain Controller

Gain access to a host providing SMB services to be used for communication between hosts in the Windows 2000 domain

The Appliance Manager's
Setup > Authentication > NTLM and Kerberos page:

  • Domain Controllers tab
  • Windows 2000 Domain Controllers option
    (name and IP address)

CLI:

config.auth.windows.dc

Windows 2000 LDAP server

Gain access to a host providing LDAP services

  • To obtain generalized access to domain information
  • To configure the appliance's server account

The Appliance Manager:

  • Domain Controllers tab
  • Windows 2000 LDAP servers option (host name and IP address)

CLI:

config.auth.windows.ldap

Windows 2000 kpasswd servers

Securely set the NetCache appliance's secret key for Kerberos

The Appliance Manager:

  • Domain Controllers tab
  • Windows 2000 kpasswd servers option (IP address, and, optionally, port number)

CLI:

config.auth.windows 
kpasswd

Windows 2000 KDCs

Get Kerberos tickets to authenticate to the LDAP domain controller

The Appliance Manager:

  • Domain Controllers tab
  • Windows 2000 KDCs option
    (host name and IP address)

CLI:

config.auth.windows.kdc

Name of the Windows domain, in its full DNS form, such as domain.com

Identify the domain you want to join

Used for many purposes.

The Appliance Manager:

  • Join Domain tab
  • Windows Domain Name option (Windows 2000 domain name)

CLI:

windows_setup

Windows 2000 machine name for this appliance

Note
This is the name configured for this appliance in the target domain's Active Directory (AD).

Create the appliance's server account

The Appliance Manager:

  • Join Domain tab
  • Windows Machine Name option (appliance name configured in AD)

CLI:

windows_setup

Windows administrator credentials:

User name and password

Authenticate the appliance (administrator) to the Windows domain

The Appliance Manager:

  • Join Domain tab
  • Windows Administrator Credentials option

CLI:

windows_setup

Library Table of Contents Index Previous Next Comments