Logic bug in DNS checker

[asuth]

Using a simple bucket name caused the bucket name to be marked as non-DNS compatible.

[tpyo]

Sorry for the late follow up. Could you give an example of a bucket name that would fail?

[asuth]

I think it was something like "subdomain.example.com"

[edwardrf]

I would like to double confirm the error.

The current code is

if (strlen($bucket) > 63 || !preg_match("/[^a-z0-9\.-]/", $bucket)) return false;

Means
for any bucket name is longer than 63 characters it is not a valid domain name OR
for any bucket name that does NOT contain anything OTHER THAN a-z0-9.- is not a valid domain => bucket name contains only a-z0-9.- is NOT a valid domain name, which is false.

However because the us standard bucket accepts both syntax of:

PUT /bucketname/uri
Host: s3.amazon.com

OR

PUT /uri
Host: bucketname.s3.amazon.com

The faulty logic listed above is always generating the 1st type of request, and when the bucket is not a us-standard, it would ask you to specify the endpoint, which cause the code to fail.

How to reproduce, create a bucket using none us standard, and try upload using the code.

[tpyo]

Thanks for reporting this. Apologies for the delayed fix.