Internally, when the Teradata JDBC Driver runs COP discovery, it appends "cop1" to the database hostname, then proceeds to cop2, cop3, cop4. The driver will continue running DNS lookups sequentially until it encounters an unknown COP hostname. Alternatively, if you have enabled the COPLAST connection parameter, the driver runs DNS lookups until it finds a COP hostname whose IP address matches the coplast hostname. For more information on the COPLAST connection parameter and the coplast hostname, see the Teradata connectivity documentation.

When a client connects to a Teradata database through a JDBC URL, the client provides the hostname without the COP suffix and the driver selects a COP entry to attempt to connect. If the first COP entry fails, the driver tries another.