Allow wildcard sub-sub-domains and sub-domains together about docker-swag

[j0nnymoe]

EXTRA_DOMAINS=*.server1.example.com,*.server2.example.com should do it.

[skylord123]

It would be great to be able to specify *.*,* for the sub-domains so you cover all first and second level sub-domains (or however deep the user wants to go).

[Ozzah]

So if we don't necessarily need *.*.example.com but we want, say, *.example.com and *.server1.example.com and *.server2.example.com, then how can that be achieved?

I just set up:

 - URL=example.com
 - EXTRA_DOMAINS=server1.example.com,server2.example.com
 - SUBDOMAINS=wildcard
 - VALIDATION=dns
 - DNSPLUGIN=cloudflare

and I got the following error:

Requesting a certificate for *.example.com and 2 more domains
An unexpected error occurred:
The request message was malformed :: Error creating new order :: Domain name "server1.example.com" is redundant with a wildcard domain in the same request. Remove one or the other from the certificate request.

[Roxedus]

This is not our restriction, it is letsencrypts restriction, its not something we can support.

You want to use the extra_domains variable to escape globbing and use * if you want *.test.example.com. This is why our readme explicit call out that you need to use "wildcard" as the subdomain.

[skylord123]

Ah you are right. *.*.example.com is not valid. I should have known better.

I also missed the EXTRA_DOMAINS variable. For some reason I thought it was only for top-level domains.

It may be a good idea to explain that wildcard doesn't support sub-sub-domains in the readme and that those need to be defined separately in the EXTRA_DOMAINS.