Determining the SPN for Each Node - Analytics Database - Teradata Vantage

Teradata Vantage clients use Service Principal Names (SPNs) to specify the Vantage node to which they want to connect.

SPNs use the following format:

service_name/instance@realm

service_name

Requests the service, that is, a Teradata Vantage.

Example: Example1

instance

Specifies the Fully Qualified Domain Name (FQDN) for a database node composed of:

• A name created in Creating a Computer Component for Database Nodes Server, for example, tdExample1-1.
• The domain path to the node, taken from Adding a Database Node to the Windows DNS, in the form: subdomain.domain.com
  The domain information you enter for instance is case sensitive. Even if the domain name has upper case characters, you must be specify it in the ktpass command using lowercase.

The domain information can include one or more additional sub-domain specifications if required to uniquely locate the node.

Example:

• tdExample1-1.corp12.example.com

When you use DNS CNAMEs to connect to a Teradata endpoint (such as AWS PrivateLink), use an A or AAAA record as the FQDN to create the SPN instead of using the CNAME record.

realm

The name of the Kerberos realm containing the node.

The realm information must match the Windows domain exactly including case.

The realm specified for this term can include one or more additional sub-realm specifications if required to uniquely identify the realm.

Example: CORP12.EXAMPLE.COM