Bug
In the server templates the m. option is still available
@Jamie, I also see it for cloned and sub-templates.
This is intentional, if those records were previously selected we don’t de-select them on upgrade. However, those options will disappear on a new install, or if they are de-selected in the template.
2 Likes
That’s such a thoughtful way to implement this. Kudos.
1 Like
A deprecated note next to this setting would be useful to say once deselected it is gone for good.
In the default template, I disable m.${DOM} then m.${DOM} disappears from the default template and child template = Ok but it also removes localhost.${DOM} in child templates which is fine but I thought I would mention it.
I don’t see it getting created when enabling dns or creating a new Virtual Server, bit confusing seeing m. is ticked, maybe a note as shoulders says.
maybe it has been broken for a while because I have never seen a m. subdomain.
You are right: it was there at some point in the past but has no been there for some time… even on Virtualmin systems which are a couple of years old.