Hostname errors in Dremio Cloud

Summary

An update to Dremio Cloud enforces strict hostname validation. This means that the hostname entered in the source settings must not include any additional information, i.e. "https://" or extra parameters such as "?useSSL=true". If your source config contains extra information in the host name field, the connection will fail.

Reported Issue

Errors will show as:

Hostname is not a domain address, nor a correct ip address

This could show up when adding a new source, editing the source config, or as a query error for sources that existed before this update.

In addition, when attempting to modify/delete/update a misconfigured source, the action may result in an error such as "Unexpected error occurred"

Relevant Versions

This article is relevant to Dremio Cloud and any sources that have a Host/Hostname field in the source config

Cause

A change was introduced that verifies the source hostnames do not contain additional elements or parameters. The connection fails if the hostname is not a valid host. While this has always been the recommended best practice, it was not enforced until this update. As such, there may be existing sources that need to be updated to be in line with this change.

Steps to Resolve

Please update your source config by removing anything that isn't strictly the hostname.

Example text that would need to be removed:

• "http://"
• "https://"
• "?useSSL=true"
• "?requireSSL=false"

The hostname field should look like: host.example.com or a valid IP address

Best Practices

To add these additional parameters, such as useSSL=true and requireSSL=false, use the Connection Properties under the Advanced Options tab.

For example, see https://docs.dremio.com/cloud/sonar/data-sources/external/mysql#advanced-options for more information on doing this for MySQL