DNS errors when using an internal minio server on LAN for S3/https #16962
Description
I am running a minio server internally. It is not exposed to the internet, and is accessed locally and via VPN.
I have DNS configured to point to it, and I've issued a certificate for it with pfsense. The pfsense root certificate and intermediate certificate have been added as trusted to the workstation that's running cyberduck. I am using the "S3 (HTTPS) template.
Cyberduck version 9.1.3 (42945)
I am able to access my minio server and the buckets in it just fine when I connect by IP (using HTTPS). However, when I connect using the domain name, and try to access any of the buckets on the minio server, cyberduck throws a DNS error. It appears to be expecting that each bucket is added as a subdomain.
I am new to S3 so maybe this is expected behaviour. I would appreciate any help with this.