The `baseDomains`/`subDomains` separation is a bit confusing

I feel like the `baseDomains`/`subDomains` separation is kind of confusing. I'm sure there's a good reason for it and it helps separating host configuration and modules, but It's hard to really understand without some example modules. The naming doesn't really help either because `subDomains` are not sub domains of `baseDomains`. I don't really have any better suggestions though. At least not without looking at some examples and understanding the intention better. Imo the UX could also be improved a bit for people who don't write reusable modules for their host setups. At the moment it requires me to define all my domains twice, so I added this hack to my config: ```nix config.networking.domains.subDomains = mapAttrs (_: _: mkDefault { }) config.networking.domains.baseDomains; ``` I'm not sure whether that's a good idea or not, because I don't really understand the intent well enough. Great module otherwise, by the way!