DNS errors when using an internal minio server on LAN for S3/https

[ioctl2]

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.

[AliveDevil]

Please configure your DNS to support Virtual Host style requests (CNAME wildcard to your Minio Domain), or use the AWS Deprecated Path Style requests-profile.

[ioctl2]

I was able to get it to work with the profile that you suggested. Thank you for that.
I don't think pfsense has the ability to support Virtual Host style requests, if I'm understanding correctly.
Maybe this is a little beyond the scope here but what do people who self host S3 typically use for DNS (to be compliant with the default profile in cyberduck)?

[AliveDevil]

When your RasPI has a static IP, you can set wildcard A records: https://docs.netgate.com/pfsense/en/latest/services/dns/wildcards.html

For DHCP assigned addresses, dnsmasq seems to support this: https://serverfault.com/questions/853282/is-it-possible-to-add-a-wildcard-cname-into-dnsmasq
I haven't found hints on whether unbound supports CNAME wildcard resolution, so you'd have to perform some research here.