Apply Configuration Rule To Wildcard

[RyderCragie]

As per my comment here, I would like to set up a Configuration Rule for my wildcard DNS record. However, I do not want it to apply to any subdomains that already have a dedicated DNS record. How can I specify this in the Configuration Rule?

[smarsh]

Configuration Rules has no way of knowing if its a defined DNS record or a wildcard.

You’ll need to manually define each DNS record in the Configuration Rule which you dont want the setting applying to, i.e. ‘hostname not in (a.b.com, b.b.com, …)’.

[RyderCragie]

Thanks for your answer.

Any plans to add this functionality?

[RyderCragie]

Further to this…

@RyderCragie

I’ll explain how I’ve set this up, as I am very confused about something and I’ve been thinking about it for over an hour now and I can’t wrap my head around it.

I have created a Configuration rule. This is what it looks like:

My primary setting is this:

My DNS looks like this:

So if it doesn’t match any of the records I’ve added, it’ll set it to Full, by the Configuration Rule.
Otherwise, it sets it to Full Strict, by the primary setting.

So in theory, Full Strict should be off for the wildcard and on for everything else. Right? There doesn’t seem to be a way to check this without going by whatever I’ve set up. There’s no “Tester” for it.

If I were to set up a new website on a new subdomain, say through Google Sites (which provides valid SSL, so would be fine with Full Strict - I think), would I need to add it to my Configuration Rule or not? What SSL setting would it be set to if I didn’t modify anything?

My brain will not compute the ifs and buts for this. I’ve no idea which way around it needs to be. If I think anymore I’ll have steam coming off the top of my head and might lose a few brain cells.

Please can someone clarify this?