You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Currently fmDNS creates a zone with a DNAME record for each clone of a domain. This is not always desirable, because for example you're not able to receive email on those clones (CNAME/DNAME in MX is NO!).
The functionality I'm looking for is to be able to set a global mode to (dis)allow the use of DNAME for cloning. And furthermore the ability to override this behaviour on a per clone basis.
I think a lot of the core functionality (FULL/DNAME output) is already in place, since the code already switches to FULL-output once you add a MX record to the clone...
The text was updated successfully, but these errors were encountered:
Interesting point and thank you for bringing it up. I'll look into how this could be down by adding a checkbox to the fmDNS settings page and then another one in the zone config page. I should be able to get this out with 2.0.
Aside from mx records, what other scenarios would somebody not want to use a dname? I can't think of any and perhaps just checking for defined mx records and if they exist then don't use a dname otherwise use a dname.
Automatic checking would be a nice feature, but would result in almost never using DNAME. In most situations you (read I) want to receive email on the main TLD and the county TLDs the company is active in (or only home country TLD). So all other country TLDs which are only used for redirection to the main TLD would be perfectly fine as a DNAME.
Here is an (really old) piece on another reason not to use DNAME: